Pike-devel January 2022

pike-devel@lists.lysator.liu.se

3 participants
4 discussions

Re: Playing music using pike and SDL.
by Martin Nilsson (lvl 60) ＠ Pike (-) developers forum 03 Dec '25

03 Dec '25

Were you not able to get any C code to play through SDL either? Does your SDL library have a mixer compiled in it (I think it is optional)?

3 2

Pike 8.0 beta 8.0.1738
by H William Welliver 01 Feb '22

01 Feb '22

Hello all- I’ve prepared a new 8.0 beta release and have uploaded it to: http://pike.lysator.liu.se/pub/pike/beta/8.0.1738/Pike-v8.0.1738.tar.gz This release is more or less green across the board. I’d like to get some feedback on binary builds, so if anyone has more than one system alike, I’d be appreciative if you could do a make bin_export and then test the result somewhere else. Any comments or problem reports are welcome… if I don’t hear any complaints in the next week or so, I’ll announce this as an official stable version and start trying to remember how I did the last windows build :/. Thanks in advance! Bill

2 1

mktestsuite and m4
by william＠welliver.org 25 Jan '22

25 Jan '22

I've traced down some problems running the testsuite on systems that ship with a non-gnu m4. Specifically, mktestsuite calls m4 with the "-d" argument. Using gm4, the lack of flags implies the a,e and q flags. On BSD m4, the "-d" argument /requires/ flags, though the flags themselves are the same as GNU m4. POSIX/Solaris/illumos m4 doesn't support the debug argument at all. Looking at mktestsuite, it tries to determine whether it's using GNU m4, and will prefer (but not require it) it should it find one. Once it's chosen the m4 binary, it seems to assume that GNU options are acceptable. Since that doesn't work, I'm wondering what the preferred ought to be: 1. require GNU m4 2. just use the full -d argument and hope (solaris/etc) users will figure out they need gm4 3. try to detect what sub-flavor of non-GNU m4 is being used I don't recall the last time I ran across a solaris system without the gnu build tools. I'd be inclined to take option 2 since it shouldn't break anyone and will improve the situation for some. A more elaborate solution could be considered if some POSIX purists complain later. Thoughts? Bill

2 1

pike-stable 7.8/SSL test failures
by william＠welliver.org 15 Jan '22

15 Jan '22

Hello all- I've been looking at some test failures in the stable tree (I haven't looked at whether they're present in the development tree yet) occurring in the 7.8/SSL testsuite. The failures happen on netbsd and illumos at a minimum, and I'm not able to see what's actually wrong, as the a/b values are equal. Examples can be found in this verifylog.txt: https://paste.sr.ht/~hww3/6fca76d6c19743525e0b1f7325fea4213b100ecd#http://p… The original file is: http://pike.lysator.liu.se/generated/pikefarm/results/8.0/6652_154/verifylo… So, if o->a==o->b, then why is the test failing? These are not new failures, but if there's a simple solution, I'd like to fix them. Any thoughts? Bill

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel January 2022