Pike-devel November 2021

pike-devel@lists.lysator.liu.se

3 participants
8 discussions

Re: Playing music using pike and SDL.
by Martin Nilsson (lvl 60) ＠ Pike (-) developers forum 13 Mar '26

13 Mar '26

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)?

5 4

managing comport settings in linux
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 13 Mar '26

13 Mar '26

Not a good idea; the design philosophy of Pike is that Pike-level code should never be able to cause memory corruption at C-level. With ioctls there's no way to know what data a specific ioctl wants without reading the documentation for that specific ioctl for that specific OS. ioctls and fcntls are a way for device handlers to hook in APIs that aren't standard across all filedescriptors. / Henrik Grubbström (Lysator) Previous text: >2004-08-17 13:32: >Subject: managing comport settings in linux >-------------------------------------------------------------------- >What would be nice, is a way to define ioctl methods in >Pike. Perhaps something like > >object i = Stdio.IOCTL(4242 /* request_id */ ); >i->add_int_parameter(); >i->add_string_parameter(); >i->set_return_type(STRING); > >string ret = i(fd, 1, "somestring"); > > >That ought to be possible, or..? > > / Marcus Agehall (PacketFront) >

3 2

full MySQL 4.x support. or pike roadmap
by thomas.gusenleitner＠com-bet.com ＠ Pike developers forum 28 Feb '26

28 Feb '26

HI to all! mysql 4.x support works only with a mysql CFLAGS=-DUSE_OLD_FUNCTIONS is this correct ? are there plans to make a full 4.x support ? bye, thomas

4 4

Re: bufferdAmount or bufferedAmount?
by Chris Angelico 18 Nov '21

18 Nov '21

On Fri, Nov 19, 2021 at 10:33 AM ceder (-) Per Cederqvist @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > > This code in lib/modules/Protocols.pmod/WebSocket.pmod seems to be > missing an "e": > > //! @decl int bufferedAmount > //! Number of bytes in the send buffer. > > int `bufferdAmount() { > return sizeof(out); > } > > I guess it should be "bufferedAmount", not "bufferdAmount"? Yep, I'd agree. It's entirely possible there's code in the wild depending on the misspelled version though. Might be worth adding the correct one and leaving the existing one as a deprecated alias for it. ChrisA

1 0

bufferdAmount or bufferedAmount?
by ceder (-) Per Cederqvist ＠ Pike (-) developers forum 18 Nov '21

18 Nov '21

This code in lib/modules/Protocols.pmod/WebSocket.pmod seems to be missing an "e": //! @decl int bufferedAmount //! Number of bytes in the send buffer. int `bufferdAmount() { return sizeof(out); } I guess it should be "bufferedAmount", not "bufferdAmount"?

1 0

compile of pike under chroot failing
by cheese＠nosuchhost.net 11 Nov '21

11 Nov '21

hi i'm currently building rpms of pike 8.0 for fedora35 and have troubles to "install" the binaries. my setup: mock (chroot environment for building rpms). inside of that environment there are several steps, mainly extract source-files, prepare, compile, install and collect the final binaries. the install step for both x86_64 and aarch64 seems to stop at: Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.bdeWDr + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64 ++ dirname /builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64 + cd Pike-v8.0.1116 + buildroot=/builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64 + rm -rf /builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64 + cd build + /usr/bin/make buildroot=/builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64 install 'INSTALLARGS=buildroot='\''/builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64'\'' lib_prefix='\''/usr/lib64/pike80'\'' include_prefix='\''/usr/include/pike80'\'' --traditional' Makefile:478: warning: ignoring prerequisites on suffix rule definition Makefile:524: warning: ignoring prerequisites on suffix rule definition make[1]: Entering directory '/builddir/build/BUILD/Pike-v8.0.1116/build' Makefile:478: warning: ignoring prerequisites on suffix rule definition Makefile:524: warning: ignoring prerequisites on suffix rule definition make[1]: Leaving directory '/builddir/build/BUILD/Pike-v8.0.1116/build' make[1]: Entering directory '/builddir/build/BUILD/Pike-v8.0.1116/build' Makefile:478: warning: ignoring prerequisites on suffix rule definition Makefile:524: warning: ignoring prerequisites on suffix rule definition make[1]: Leaving directory '/builddir/build/BUILD/Pike-v8.0.1116/build' Installing Pike in /builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64/usr, please wait... i'm waiting for several hours (around 16) now attaching with strace to the running pike gets me: close_range(11, -1, 0) = -1 EPERM (Operation not permitted) openat(AT_FDCWD, "/proc/self/fd/", O_RDONLY|O_DIRECTORY) = 9 getdents64(9, 0x7ffdc355bb80 /* 13 entries */, 1024) = 312 getdents64(9, 0x7ffdc355bb80 /* 0 entries */, 1024) = 0 close(9) = 0 close_range(11, -1, 0) = -1 EPERM (Operation not permitted) openat(AT_FDCWD, "/proc/self/fd/", O_RDONLY|O_DIRECTORY) = 9 getdents64(9, 0x7ffdc355bb80 /* 13 entries */, 1024) = 312 getdents64(9, 0x7ffdc355bb80 /* 0 entries */, 1024) = 0 close(9) .... fast looping over that lines any ideas? the same under fedora 34 built correctly. any suggestions? yours josef

3 4

mailling list archive not complete
by cheese＠nosuchhost.net 10 Nov '21

10 Nov '21

hi i see some mails in my inbox from pike-devel which are missing in the online archive at http://lists.lysator.liu.se/pipermail/pike-devel/2021-October/date.html eg. the answers for "New Pike 8.0 release?" from william are missing online. yours josef

1 0

New Pike 8.0 release?
by william＠welliver.org 10 Nov '21

10 Nov '21

It's been about a year since the last release, and I've found a number of configure problems on "apple silicon". How about we start the process of a new 8.0 release? Perhaps starting 2 weeks from today? If there are no objections, I'll start cutting release candidates at that point. I'll send a reminder when about a week is left. Bill

3 2

2026

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 November 2021