Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

How to dump pike modules in a fakeroot/sandbox environment?
by Rainer Groesslinger 11 Dec '03

11 Dec '03

Hi, I am having a problem building pike in a fakeroot/sandbox'ed environment and *additionally* dump the pike modules. (to avoid those problems you surely have heard about hundred times when building in a fakeroot and then try to run a pike application using a module: /usr/lib/pike/.../.../whatever.pmod.o:-: Warning: Decode failed: Failed to decode program) The problem I am having is, pike seems to be able to dump the modules when installing in a fakeroot environment from what I can read in the install scripts but it cannot do it without violating the sandbox (e.g. writing outside the fakeroot). In short, I do the following (after pike was built using make CONFIGUREARGS="..." etc.): sed -i s/rm$mod\+\"\.o\"$\;/\{\}/ for install.pike, which results in the following: --- install.pike.orig +++ install.pike @@ -1096,7 +1096,7 @@ rm("dumpmodule.log"); foreach(to_dump, string mod) - rm(mod+".o"); + {} // Dump 25 modules at a time I need to do this, because otherwise the sandbox is violated since pike directly wants to do some action in /usr/lib/... Then I use the following command to install pike: make INSTALLARGS="--traditional" buildroot="${D}" install ("${D}" being the virtual "/") Because of the change to install.pike, the modules aren't dumped automagically, and to be honest, I feel a bit lost now how I can dump the modules to avoid those fakeroot/decode problems with the modules, but without violating the sandbox. Thanks in advance for your answers, -- Rainer Groesslinger <rainer.groesslinger(a)gmx.net>

2 3

client-server/agent testsuite
by Mirar ＠ Pike developers forum 10 Dec '03

10 Dec '03

Is there any smooth way to test the Pike Protocols, for instance for client/server applications where you need to be asynchronous or to spawn off subprocesses? Is it possibly to design such a setup?

2 4

is there a fully supported win32 build available ?
by Jed Adams 09 Dec '03

09 Dec '03

according to the latest release 7.4.31 DVB................. no (dependencies failed) FFmpeg.............. no (dependencies failed) GTK.GlArea.......... no (dependencies failed) GTK.GladeXML........ no (dependencies failed) Gdbm................ no (dependencies failed) Gnome............... no (dependencies failed) Image.SVG........... no (dependencies failed) Image.TIFF.......... no (tifflib version 42) Mird................ no (no system libmird, can not use included) Oracle.............. no (dependencies failed) PDF.PDFlib.......... no (dependencies failed) PDF.Panda........... no (dependencies failed) Perl................ no (forced without) Postgres............ no (dependencies failed) SDL_mixer........... no (dependencies failed) Ssleay.............. no (forced without) now out of all of these i'm really interested in GTK.GlArea and also the build i have doesn't have GLUT support either i've looked at most of the samples and the few i can find for GL use either of these so my question is , is anyone working on either of these ? or is there a nice tutorial on building the whole shebang on windoze ? thamks for your time Jed

3 2

"thread_create"
by Jaroslaw Sitek 08 Dec '03

08 Dec '03

Hello I would like to ask if there were any changes in implementing threads between version 7.2 and 7.4 (stable) or rather what exactly has changed? The code of my function (implemented in master): object _load_thread(string path, mixed ... args) { program prg = _compile(path); string objid; object obj; array(string|int) err; if (objs[path]) return objs[path]; if (!prg) return 0; err = catch { obj = prg(@args); thread_create(obj->run); }; if (err) { werror(err[0]); werror(describe_backtrace(err[1])); } ... works perfectly in version 7.2, it creates suitable number of threads when it is called on a given objects. But the same function called on the same objects in version 7.4 creates only one (first) thread and though the compiler doesn't return any error messages when the function is initialized, threads are not 'loaded'. To check if threads are created I simply: ps aux|grep pike There are no names of threads, just the process is visibly divided into as many threads as the number of objects called in individual call. Could anyone tell me what is the problem? My system: Linux, Debian, i686 Aron@Valhalla

1 0

program(x)
by Mirar ＠ Pike developers forum 08 Dec '03

08 Dec '03

It seems to do something (I got an illegal assigment for x=peer_program() if I changed the type), but PikeParser doesn't allow it.

1 1

program(x)
by Mirar ＠ Pike developers forum 08 Dec '03

08 Dec '03

Is the construct program(x) legal, or even useful? It seems to be allowed. I would like to constraint a variable to only be able contain programs compliant to a certain class.

1 0

call_callback
by Mirar ＠ Pike developers forum 08 Dec '03

08 Dec '03

And call_outs.

2 4

call_callback
by Mirar ＠ Pike developers forum 08 Dec '03

08 Dec '03

Is there any utility function in Pike that does the following, or an approximate? void call_callback(function f,mixed ... args) { mixed err; err=catch { f(@args); return; }; werror(master()->describe_backtrace(err)); } ...preferably with typechecking. I find that I would like to put a wrapper around my callbacks a lot of the time, to be certain that the code following still is run even if the user (of my library-ish routines) makes an error.

4 6

Problems with MIME.Message
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 06 Dec '03

06 Dec '03

>The first one is a typical problem I get with mails from Eudora. You can >find the mail at http://qo-op.com/break_mime.txt The problem with this one is that the boundary delimiter of the outer multipart occurs as a prefix of the boundary delimiter for the inner multipart. RFC2046 explicitly forbids this: As stated previously, each body part is preceded by a boundary delimiter line that contains the boundary delimiter. The boundary delimiter MUST NOT appear inside any of the encapsulated parts, on a line by itself or as the prefix of any line. This implies that it is crucial that the composing agent be able to choose and specify a unique boundary parameter value that does not contain the boundary parameter value of an enclosing multipart as a prefix. Complain to the makers of Eudora. >Next is the error log I get from the LMTP server included in Pike 7.5. >It shows that MIME.Message simply brokes really too much. I run the LMTP >server with Pike 7.2.526 in Caudium. The problem here is the Content-Type line: Content-Type: text/html;iso-8859-1 This is a syntax error. It's supposed to be Content-Type: text/html;charset=iso-8859-1 Again, it's the mail that is broken, not MIME.Message. / Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) Previous text: >2003-12-05 16:20: >Subject: Problems with MIME.Message >-------------------------------------------------------------------- >Hi, > >Last time I mail the Pike devel list about problems with MIME, you ask >me for some examples. Here are some I get on a production server. >I contact your privately since some of the data you can find in these >emails are private. > >The first one is a typical problem I get with mails from Eudora. You can >find the mail at http://qo-op.com/break_mime.txt > >With Pike 7.2.526 it fails with: > >multipart message improperly terminated >/usr/local/pike/7.2.526/lib/modules/MIME.pmod:880: > create("Content-Type: >multipart/related;\n\ttype=\"text/html\";\n\tboundar > y=\"=====================_197842502==_.REL\"\n",0,0) > >MIME: Message() > >And with 7.4.31: > >boundary missing from multipart-body >/usr/local/pike/7.4.31/lib/modules/MIME.pmod/module.pmod:1080: > MIME.Message()->create("Content-Type: >multipart/related;\n\ttype=\"text/ht > >ml\";\n\tboundary=\"=====================_197842502==_.REL\"\n",0,0,0) >object_program(MIME): MIME->Message() >/usr/local/pike/7.4.31/lib/modules/MIME.pmod/module.pmod:1100: > MIME.Message()->__lambda_65685_4_line_1090("Content-Type: >multipart/relate > >d;\n\ttype=\"text/html\";\n\tboundary=\"=====================_197842502==_ > .REL\"\n") > > >Next is the error log I get from the LMTP server included in Pike 7.5. >It shows that MIME.Message simply brokes really too much. I run the LMTP >server with Pike 7.2.526 in Caudium. > >I've added the following debug at line 869 of MIME.pmod to help debugging: > >write("headers[\"content-transfer-encoding\"]=%s\n", >headers["content-transfer-encoding"]); >array(string) arr=tokenize(headers["content-transfer-encoding"]); >write("arr=%O\n", arr); > >The log file also contains all the contents of the mail. I've tried to >find out where the problem but I didn't succeed. > >You can find the log file at http://smtp.linkeo.org/error_log.gz > >-- David Gourdelier > > > > / Brevbäraren >

1 0

Pike benchmarks
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 05 Dec '03

05 Dec '03

Some new benchmarks 7.2.550 vs 7.4.35 vs 7.5.13 using shootout tests: Pike7.2 Pike7.4 Pike7.5 1: 5.62 4.50 2.52 (ackermann) 2: 10.27 6.72 6.84 (ary3) 3: 8.55 6.62 6.42 (fibo) 4: 5.92 4.78 4.61 (hash) 5: 11.05 7.22 6.09 (heapsort) 6: 7.46 6.69 6.56 (lists) 7: 8.19 8.25 6.09 (methcall) 8: 54.21 5.91 6.47 (nestedloop) 9: 6.04 5.23 4.99 (objinst) 10: 7.29 4.79 5.21 (random) 11: 9.95 6.71 4.54 (sieve) 12: 3.13 2.33 2.50 (strcat) Scoring based on position in tests (should probably be updated to include difference in percent): 1: Pike7.5 32 2: Pike7.4 27 3: Pike7.2 13

2 9

Jump to page:

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