Pike-devel May 2017

pike-devel@lists.lysator.liu.se

4 participants
6 discussions

GTK/GDK on OSX
by H William Wellliver III 08 Jan '18

08 Jan '18

I’m running into some build problems on OSX. It seems that the GTK module assumes that if a system is NT that gdkwin.h is used and otherwise gdkx.h is used. Unfortunately, it seems that on some builds of GTK/GDK for OS X, neither of those is correct and that gdkquartz.h should be used. I’m guessing that some configure tests are needed to determine which of the 3 files is actually present. However a quick look at configure.in leaves me unsure how best to include that. Anyone with more expertise in the GTK module’s inner workings care to weigh in? Bill

4 9

Proposal: Create Stdio.Port from systemd-provided socket
by Chris Angelico 22 Nov '17

22 Nov '17

Branch: rosuav/systemd-sockets Currently, you can create a Stdio.Port("stdin") as a means of accepting a socket handed to you as FD 0. However, there's no way to accept a socket given as any other FD, making it impossible to use this for systemd's sockets. Example: $ cat /etc/systemd/system/listendemo.service [Unit] Description=Listen Demo Requires=listendemo.socket [Service] User=rosuav ExecStart=/usr/local/bin/pike /home/rosuav/listendemo.pike WorkingDirectory=/home/rosuav $ cat /etc/systemd/system/listendemo.socket [Socket] ListenStream=123 $ cat listendemo.pike object mainsock = Stdio.Port("systemd", acceptloop); void acceptloop() { while (object sock=mainsock->accept()) { write("Accepted sock: %O\n", sock); sock->write("Stub\n"); sock->close(); } } int main() { write("Main sock: %O\n", mainsock); return -1; } Note that the "User=rosuav" directive means that Pike is run as a non-root user. This spares the application the hassle of managing privileges securely, as it never gets root privileges (assuming, of course, that the only reason it needed root was to bind to a privileged port, which is true for a lot of programs). As with "stdin" mode, the second parameter is optional (blocking vs nonblocking). This won't break on non-systemd systems for two reasons: firstly, all it ever does is query environment variables, and secondly, it does this only if the application requests it explicitly, so you have to actually ask for it. Is this something that would be useful? Feel free to bikeshed the API - it's not in 8.1 yet, so anything can change. ChrisA

3 6

Major problem with SQLite binding handling
by H. William Welliver III 22 Jun '17

22 Jun '17

I’ve noticed an odd problem a few years ago with using parameter bindings with SQLite and never really took the time to figure out the cause until now. I think it’ a pretty major problem that can be easily fixed, though would cause problems for anyone relying on the (imo) currently broken behavior. Basically, the problem is that when using parameter bindings with strings, the pike glue determines the type of the data based on the width of the string: if it’s a wide string, the parameter is bound as a text, but if it’s 8 bit, it’s bound as a blob. The problem is that text and blob values aren’t evaluated the same, so even though a text value and blob value may be identical byte-wise, they are not equal when doing comparisons and so queries that would seem to match actually don’t. This is compounded by the fact that SQLite has no restrictions on what may be stored in a field (type definitions on a table are merely default suggestions) and SQLite will happily store whatever you want (such as a blob value in a text field). For example, imagine a table m with an integer field id and a char field value: s->query(“INSERT INTO m VALUES(1, 'value a’)); s->query(“INSERT INTO m VALUES(2, :value)”, ([“:value”, “value a”])); s->query(“SELECT * FROM m where value=‘value a’”); The third query will return 1 record instead of the expected 2 because the field value in the second row is stored as a blob and thus does not match a text query. In order to retrieve both records, you must use LIKE or know to cast the value to text using “AS TEXT” in the query, which is obviously a lot less ideal in most cases. If all of your data is stored using the pike glue, and you’re always using parameters, it’s possible never to see the problem, but if not, this causes all kinds of problems because of the need for constantly casting values and possibly using blob literals, which are not human readable when you’re really trying to query for a non-wide string. My suggestion is to change the binding type for 8 bit string parameters to text in order to match the rest of the string handling. It would be good to have a datatype that caused a parameter to be bound as a blob, either a native byte array or some object that wraps an 8 bit string (Sql.BinaryString?) in order to cause the binding to act accordingly. Of course, this causes a compatibility problem for anyone who was using pike binding with bindings previously (is there anyone who us doing this and hasn’t run into this problem?), as any 8-bit strings that weren’t binary data would be stored as blobs, even if they were in a text typed field. These records would need to be re-stored with the proper text type, which could be done with a query to update the table. My sense is that this is the proper thing to do, as blob fields should be reserved for data that’s actually binary data (as opposed to text). Thoughts?

3 3

GDK/GTK on OSX
by H. William Welliver III 30 May '17

30 May '17

Note: I actually sent this email to Chris a month ago but it didn’t go to the list, so I’m sending it there so that there’s a record of this conversation. Hi Chris, I’ve been quietly working on this for a few weeks now, and have got the various permutations working on OS X. Basically, there are 2 paths for GTK on OS X (now called macOS): X11, which is the classic approach, and Quartz, which is native, but newer and a little less fully baked. Homebrew, a very popular package manager on OS X, switched to Quartz mode at some point, which broke the pike builds. This sort of dual mode situation affected GL and GLUT as well. So, I’ve arrived at a solution where we prefer the native Quartz versions but will fall back if they’re not present (such as if you happen to be running the Darwin open source OS that macOS is based on. I think that’s the most reasonable approach because every macOS install will have Quartz, GL and GLUT (and using GTK doesn’t require you to install X11/XQuartz. I’ve merged your change into 8.1 and 8.0 after testing, along with a bunch of other fixes to get things working. I have not been able to verify that the changes work properly on Windows because I am having trouble getting the windows build to compile successfully. Likely because I foolishly tried to upgrade to VC2015 from VS2008, which was working properly. There are also a number of problems with other bits of the 8.1 codebase that cause problems on Windows, though I see some commits lately that seem to suggest that may be a temporary thing. Anyway, that’s the current update. And to answer your question about being able to run gtk apps on macOS without having to install X11, here’s a little taste : object x; int main() { GTK2.setup_gtk(); x = GTK2Support.Alert("Hello world!"); return -1; } Yields: http://bill.welliver.org/dist/pike/gtkmacdialog.png <http://bill.welliver.org/dist/pike/gtkmacdialog.png> Enjoy! Bill

2 2

Bad function identifier on 8.1
by Stephen R. van den Berg 30 May '17

30 May '17

While trying to use Pike 8.1, I consistently get the following on stderr whenever I run pike: /usr/local/pike/8.1.6/lib/modules/Crypto.pmod/Random.pmod.o:-: Warning: Decode failed: Error while decoding program(/usr/local/pike/8.1.6/lib/modules/Crypto.pmod/Random.pmod:23): Bad function identifier offset for random_string:function(int(0..2147483647) : string(8bit)): 3 != 0 It's not immediately obvious to me how to fix this. Anyone? Or am I the only one seeing this? -- Stephen.

2 4

pike compile failes on fedora 25 x86_64
by josef radinger 22 May '17

22 May '17

hi i try to compile pike for fedora 25 and it fails as below: ... precompile: /usr/local/bin/pike80 /tmp/Pike- v8.0.404/bin/precompile.pike --base=FSEvents /tmp/Pike- v8.0.404/src/modules/FSEvents/fsevents.cmod (method=QQQQQQ) Compiling modules/FSEvents/fsevents.c Linking FSEvents #### Making dynamic: modules/Fuse Compiling modules/Fuse/fuse.c Linking Fuse Making module.pmod #### Making dynamic: modules/Gdbm Compiling modules/Gdbm/gdbmmod.c /tmp/Pike-v8.0.404/src/pike_error.h:54:34: error: expected ‘)’ before string constant (fprintf(stderr,msg_fatal_error,__FILE__,(long)__LINE__),debug_fatal) ^ In file included from /tmp/Pike-v8.0.404/src/threads.h:11:0, from /tmp/Pike-v8.0.404/src/modules/Gdbm/gdbmmod.c:9: /tmp/Pike-v8.0.404/src/pike_error.h:54:58: error: expected ‘)’ before ‘,’ token (fprintf(stderr,msg_fatal_error,__FILE__,(long)__LINE__),debug_fatal) ^ Compilation command was: /tmp/Pike-v8.0.404/build/linux-4.10.8-200.fc25.x86_64-x86_64/smartlink gcc -I. -I/tmp/Pike-v8.0.404/src/modules/Gdbm -I/tmp/Pike- v8.0.404/build/linux-4.10.8-200.fc25.x86_64-x86_64 -I/tmp/Pike- v8.0.404/src -I/usr/local/include -DHAVE_CONFIG_H -g -ggdb -m64 - mrdrnd -fvisibility=hidden -O3 -pipe -fvar-tracking-assignments -funswitch-loops -W -Wall -Wno-unused -Wcomment -Wformat -Wimplicit- function-declaration -Wmultichar -Wunused-function -Wswitch -Wuninitialized -Wpointer-arith -Wchar-subscripts -Wno-long-long -Wdeclaration-after-statement -fPIC -DDYNAMIC_MODULE -c /tmp/Pike- v8.0.404/src/modules/Gdbm/gdbmmod.c -o gdbmmod.o Makefile:167: recipe for target 'gdbmmod.o' failed make[6]: *** [gdbmmod.o] Error 1 Makefile:100: recipe for target 'all' failed make[5]: *** [all] Error 2 Makefile:100: recipe for target 'Gdbm' failed make[4]: *** [Gdbm] Error 1 Makefile:1175: recipe for target 'dynamic_module_objects' failed make[3]: *** [dynamic_module_objects] Error 1 Makefile:1195: recipe for target 'module_objects' failed make[2]: *** [module_objects] Error 2 Makefile:149: recipe for target '_make_in_builddir' failed make[1]: *** [_make_in_builddir] Error 2 Makefile:66: recipe for target 'compile' failed make: *** [compile] Error 2

2 3

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 May 2017