Pike-devel April 2003

pike-devel@lists.lysator.liu.se

11 participants
55 discussions

What am I missing?
by Ryan Elgram 19 Apr '03

19 Apr '03

Running FreeBSD 5.0 Making GL Linking GL /usr/bin/ld: cannot find -lGL Linking failed: /usr/local/downloads/Pike-v7.4.20/bin/smartlink /usr/local/downloads/Pike-v7.4.20/build/freebsd-5.0-current-i386/smartlink gcc -Wl,-Bshareable -static-libgcc -I/usr/X11R6/include -I. -I/usr/local/downloads/Pike-v7.4.20/src/post_modules/GL -I/usr/local/downloads/Pike-v7.4.20/build/freebsd-5.0-current-i386 -I/usr/local/downloads/Pike-v7.4.20/src -DHAVE_CONFIG_H -I/usr/local/include -I/usr/X11R6/include -I/usr/local/include/pth -pipe -fPIC -DDYNAMIC_MODULE -O -o module.so top.o auto.o -g -O2 -pipe -I/usr/local/include/pth -L/usr/local/lib/pth -lGL -lm -lpthread -lcrypt /usr/lib/libgcc.a -lc /usr/lib/libgcc.a *** Error code 1 Stop in /usr/local/downloads/Pike-v7.4.20/build/freebsd-5.0-current-i386/post_modules/GL. *** Error code 1 Stop in /usr/local/downloads/Pike-v7.4.20/build/freebsd-5.0-current-i386/post_modules/GL. *** Error code 1 Stop in /usr/local/downloads/Pike-v7.4.20/build/freebsd-5.0-current-i386/post_modules. *** Error code 1 Stop in /usr/local/downloads/Pike-v7.4.20/build/freebsd-5.0-current-i386. *** Error code 1 Stop in /usr/local/downloads/Pike-v7.4.20/build/freebsd-5.0-current-i386. *** Error code 1 Stop in /usr/local/downloads/Pike-v7.4.20.

2 1

FreeBSD 5.0
by Ryan Elgram 18 Apr '03

18 Apr '03

I am having some difficulties compiling under FreeBSD 5.0. I have installed libgmp4 but the pike install never seems to find it. If I install without-bignums ... it will configure fine, but during make I am getting some errors about it not being able to locate pike to run something.pike. Does anyone have an special considerations they would like to share when installing under FreeBSD?

2 2

predef::Iterator
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 18 Apr '03

18 Apr '03

Why is the function that creates the basic iterators called "Iterator" like a class? Now it gets tricky to add an interface class for iterators, since the obvious name for it already is taken. :(

2 5

libkse + freebsd ?
by Xavier Beaudouin 17 Apr '03

17 Apr '03

Hey there, On FreeBSD 5.0, we can have KSE (Kernel Threads) with posix interface with linking with -lkse... Can we add that on Pike 7.5 automatically ? and if so, how, because threads detector in configure.in is somewhat confusing... Maybe we try to detect pthread_create() on -lkse ? /Xavier PS: I add a new pikefarm server RSN :)

2 2

Re: Starting new pike processes from the testsuite
by Mirar ＠ Pike developers forum 15 Apr '03

15 Apr '03

Ah, yes, there is already a SSLPort class. Great. Nevermind then :) / Mirar Previous text: >2003-04-15 17:43: >Subject: Re: Starting new pike processes from the testsuite >-------------------------------------------------------------------- >There should be https server code in the 7.4+ tree, as I'm pretty sure I >committed my changes... > >Bill > >On Tue, 15 Apr 2003, Mirar @ Pike developers forum wrote: > >> If there is HTTPs server code, it probably belongs - would be great - >> in the Protocols.HTTP.Server tree. >> >> / Mirar >> >> Previous text: >> >2003-04-15 11:16: >> >Subject: Starting new pike processes from the testsuite >> >-------------------------------------------------------------------- >> >What's the recommended way of starting separate processes (which are >> >Pike programs) from the testsuite? >> > >> >I want to make a test case for the SSL code, by starting a https >> >process using the SSL.pmod/https.pike program (which I'm not sure it >> >really belongs in the module tree) or some similar code, and then use >> >the client code in the url/http modules to connect to it. >> > >> > / Niels Möller (ny flexiblare bröstkorg) >> > >> > > > > / Brevbäraren >

1 0

Starting new pike processes from the testsuite
by Niels M�ller (ny flexiblare br�stkorg) ＠ Pike (-) developers forum 15 Apr '03

15 Apr '03

Ok, that crash disappeared after a recompile. Good.

1 0

nasties in Stdio
by rjb ＠ Pike developers forum 14 Apr '03

14 Apr '03

Two problems/inconsistencies: Stdio.FakeFile.read(len) will return 0 if len is more than there is data left to read. This is inconsistent with Stdio.File.read(len), which returns less than len, an empty string if no data is left (for a disk file at least). Stdio.Stream declares a prototype string read(int nbytes); and does not allow for a second argument not_all (which would work around the previous issue). Together this creates problems when writing a function to operate on a Stdio.Stream (open for reading), when you want to be able to drop in an instance of either a Stdio.File or a Stdio.FakeFile at runtime. (I checked this on 7.4, can't look at 7.5 right now because the cvs browser seems to be broken) /rjb

2 1

MySQL V4
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 14 Apr '03

14 Apr '03

I have reverted the MySQL V4 changes to 7.4, since they stopped Pike from working with MySQL V3. In the future, please put experimental changes into 7.5, and then backport them after they have been proven correct by pikefarm.

1 0

MIME multipart message improperly terminated bug [3414]
by Martin Nilsson (har bott i google) ＠ Pike (-) developers forum 14 Apr '03

14 Apr '03

Spontaneous thought; Caudium truncates the data it sends to MIME (timeout?). Wasn't this a also problem in WebServer that has been fixed? / Martin Nilsson (har bott i google) Previous text: >2003-04-13 22:59: >Subject: MIME multipart message improperly terminated bug [3414] >-------------------------------------------------------------------- > > Product: Pike > Version: 7.4 > Component: Modules > Reporter: funk(a)softhome.net > URL: https://community.roxen.com/crunch/show_bug.cgi?id=3414 > >I'm using pike 7.4.21 with the Caudium web server. I've noticed a bug >related to uploading files using MIME attachments. IT seems that small >files work fine, however larger files do not. The web browser keeps saying >it's loading, but the caudium log gives error ouput as follows: > >multipart message improperly terminated ("\r\nContent-Disposition: >form-data; name=\"file\"; filename=\"drummer.png\"\r\nContent-Type: >image/png***Here it shows the text ouput of the file i cut it out to save >lots of space in the bug report*** ) >/usr/local/pike/7.4.21/lib/modules/MIME.pmod/module.pmod:1078: >MIME.Message()->create("-----------------------------47449013511489176341833204461\r\nContent-Disposition: >form-data; name=\"file\"; filename=\"drummer.png\"\r\nContent-Type: >image/png\r\n\r\n\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\1g\0\0\1j\b\6\0"+[16854],mapping[11],0,0) >object_program(MIME): MIME->Message() >protocols/http.pike:200: protocols/http()->handle_body_encoding(21665) >protocols/http.pike:455: protocols/http()->parse_got() >protocols/http.pike:1657: >protocols/http()->got_data(0,"7\366$\336\31t\34\223\245\314)\262r\16\302\361D_\25\36PjZuk\27\7!\301""6\345D9s\224\277\7\341\317N|\24\215\255\234\233\220ES\355\273\274\36\361\310\310\373\354\350u\340-\334\23\212q\210\37\177=\322\216[9\367 >\35\345<\31\231\350\254\t\274\215< >\343\234\261\307J\243(\347\t1\367\347\227V`\245\30\373\253\364\203nD\345\274#\372\33\322?\220\207\\n\177lU<\217\373\\\276A}+g\27q\377\336""5\345\274\21b\352*\323\216\230\275\216#\207o+Y\257\352\247\365e\335\25s\177YQiG\323L2\365ls\326r\253|I\261\24""3\300\177\225\355CS\225\"]4_\347\264"+[1254]) >/usr/local/pike/7.4.21/lib/modules/Stdio.pmod/module.pmod:695: >Stdio.File("socket", "192.168.0.2 58269", 777 /* fd=19 >*/)->__stdio_read_callback() >module.c:58()->Builtin()->Backend: >module.c:58()->Builtin()->__backend->`()(3600.000000) >/usr/local/pike/7.4.21/lib/master.pike:1951: >master()->_main(({"bin/caudium","-DCAUDIUM","-DCAUDIUM_CACHE","-DROXEN","-DMODULE_DEBUG","-w","-Mlib/7.4.21/",,,6}),({"SSH_CLIENT=192.168.0.2 >63575 22","USER=root","MAIL=/var/mail/root","SHLVL=1",,,15})) > >The log keeps repeating this until i press stop in my browser... > >Here i'll include the code i use to upload the images. > >HTML PAGE: > ><form name="imhouploadform" method="POST" enctype="multipart/form-data" >action="/(dumpid)/upload"> ><br /> ><input name="file" type="file"> ><br /> ><input type="submit" name="1" value="Upload to attachments" /> ></form> > >excerpt from Caudium Pike Module: > >mixed find_file( string f, object id ) { > string sucpage = id->variables->success; > string fpage = id->variables->failed; > string contents = id->variables->file; > string filename = id->variables["file.filename"]; > string gallery; > if (id->variables->gallery) > gallery = id->variables->gallery; > else > gallery = QUERY(defaultgallery); > string galpath = Stdio.append_path(QUERY(albumpath), gallery); > string path = Stdio.append_path(QUERY(albumpath), gallery, filename); > if ( contents && filename && Stdio.is_dir(galpath) && >!Stdio.is_file(path) && isgood(filename) && sizeof(contents) < >QUERY(maxsize) ) { > Stdio.write_file ( path, contents ); > return http_string_answer("Upload Succeeded","text/html"); > } > >I hope this helps someone locate and troubleshoot this bug, it's seriously >stumping my productivity... Well thanks for any help. > > > / Brevbäraren >

3 7

PCRE license
by Martin Baehr 10 Apr '03

10 Apr '03

hi, since the inclusion of PCRE is still not done, i want to discuss the one question that has not been conclusively addressed: the license. http://www.pcre.org/license.txt the last discussion ended with the comment that the points 1. 2. and 3. still apply because of the mpl. my opinion is that these points do not conflict with the mpl. and in particular the last paragraph of #2 allows anybody to include pike without limitations through pcre. so the only thing holding us back is someone to take pcre and prepare it for pike 7.5 so that it can be tested... i am repeating the points for your convenience. full license is under the url above. greetings, martin. from: http://www.pcre.org/license.txt 1. This software is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. 2. The origin of this software must not be misrepresented, either by explicit claim or by omission. In practice, this means that if you use PCRE in software that you distribute to others, commercially or otherwise, you must put a sentence like this Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel, and copyright by the University of Cambridge, England. somewhere reasonably visible in your documentation and in any relevant files or online help data or similar. A reference to the ftp site for the source, that is, to ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/ should also be given in the documentation. However, this condition is not intended to apply to whole chains of software. If package A includes PCRE, it must acknowledge it, but if package B is software that includes package A, the condition is not imposed on package B (unless it uses PCRE independently). 3. Altered versions must be plainly marked as such, and must not be misrepresented as being the original software.

3 2

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 April 2003