Pike-devel

pike-devel@lists.lysator.liu.se

3044 discussions

'-g' is forbidden in paths...
by David Hedbor ＠ Pike developers forum 01 Jun '03

01 Jun '03

This brilliant code: CFLAGS="`echo $(CFLAGS) | sed -e 's/-g//g' -e 's/-W[^ ]*//g'`" \ In the GL and GTK Makefile.in's don't do what you'd want them to do when your directory is named, for example: /mnt/disk3/src/pike/7.4/build/linux-2.4.20-gaming-r3-i686 What are the reasons for the forced removal of -g and other stuff anyway?

3 3

Codec
by Martin Nilsson (lambda) ＠ Pike (-) developers forum 01 Jun '03

01 Jun '03

In the new Codec, isn't it better to prefix strings with "\1", "\2" etc instead of "s", "p" etc, to ensure no interference with resolving e.g. q->p->r? Also, should we make the module dumper a Standalone Tool (i.e. NOT making it standalone but part of Pike), so that one can do "pike -x dump my_module.pmod"? Another idea is that "pike -x dump" redumps all module directories.

2 3

dumping modules
by rjb ＠ Pike developers forum 30 May '03

30 May '03

I tried running dumpmodule.pike on some of my .pmod's, with the result: -rw-r--r-- 1 rjb rjb 55029 May 21 11:23 PiXPull.pmod -rw-r--r-- 1 rjb rjb 82157 May 28 11:43 PiXPull.pmod.o -rw-r--r-- 1 rjb rjb 18221 May 21 11:23 PiXTree.pmod -rw-r--r-- 1 rjb rjb 102525 May 28 11:43 PiXTree.pmod.o Note the funny sizes: the module with much less code gets a significantly larger bytecode dump. Taking a closer look, I concluded that the bytecode for PiXPull.pmod was for some reason getting pulled into PiXTree.pmod.o. Indeed, running `strings' on PiXTree.pmod.o, I found all the string literals used in PiXPull.pmod. In fact, PiXTree.pmod contains the statement `import .PiXPull;', but it's not clear to me whether this should have the above effect. NB modifying PiXTree.pmod to reference .PiXPull.Parser etc. explicitly (instead of using the import) has little effect on the dump. (This is with Pike v7.4 release 21)

2 1

make problems on OpenBSD
by Ian D (spellisteligist) ＠ Pike (-) developers forum 29 May '03

29 May '03

This seems familiar in a way: (GNU Make 3.80, OpenBSD-current, Pike-7.4.20) [ian@bleep Pike-v7.4.20]$ gmake install "Makefile", line 336: Need an operator No closing parenthesis in archive specification "Makefile", line 337: Error in archive specification: "\|void\|constant\|class\)\>)*\|\<\" No closing parenthesis in archive specification "Makefile", line 337: Error in archive specification: "\t]\{1,\}\" "Makefile", line 337: Need an operator sh: syntax error: `(' unexpected "Makefile", line 340: warning: "\|->=?\|<[<=]\|==\|>[=>]\|\[\]=?\|()\|[%-!^&+*<>|~\/]\)\)[ \t]*(/\4/' -r '/" returned non-zero status Fatal errors encountered -- cannot continue gmake: *** [install] Error 1 [ian@bleep Pike-v7.4.20]$

4 3

bug report?
by Ian D (spellisteligist) ＠ Pike (-) developers forum 29 May '03

29 May '03

I couldn't find how to bug report on pike.ida: On OpenBSD > 3.2 (tested on -current), the compiler complains following: /usr/include/malloc.h:4: warning: #warning "<malloc.h> is obsolete, use <stdlib.h>" (same as freebsd, i gather)

2 1

FreeBSD - can't compile Pike
by Editor 28 May '03

28 May '03

Hi. When Compiling Caudium 1.2.8 under FreeBSD 4.8 make also attempted - and failed - to compile Pike. The compile fails with the following error message: [...] /sbin/ldconfig -m /usr/local/lib ===> Registering installation for gdbm-1.8.3 ===> Returning to build of pike72cvs-7.2.380_1 Error: shared library "gdbm.2" does not exist *** Error code 1 I'm wondering what I can do in order to successfully complete the compile. A more complete excerpt of the compilation log follows below (parts I skipped are indicated using [...]): [...] ===> Extracting for pike72cvs-7.2.380_1 >> Checksum OK for pike-7.2.380.tar.gz. ===> Patching for pike72cvs-7.2.380_1 ===> Applying FreeBSD patches for pike72cvs-7.2.380_1 ===> pike72cvs-7.2.380_1 depends on executable: bison - found ===> pike72cvs-7.2.380_1 depends on executable: nasm - found ===> pike72cvs-7.2.380_1 depends on executable: gmake - found ===> pike72cvs-7.2.380_1 depends on shared library: gmp.6 - found ===> pike72cvs-7.2.380_1 depends on shared library: jpeg.9 - found ===> pike72cvs-7.2.380_1 depends on shared library: tiff.4 - found ===> pike72cvs-7.2.380_1 depends on shared library: gdbm.2 - not found ===> Verifying install for gdbm.2 in /usr/ports/databases/gdbm If you need UNIX dbm/ndbm compatibility functions, use "make WITH_COMPAT=yes" ===> Extracting for gdbm-1.8.3 >> Checksum OK for gdbm-1.8.3.tar.gz. ===> Patching for gdbm-1.8.3 ===> Applying FreeBSD patches for gdbm-1.8.3 ===> gdbm-1.8.3 depends on executable: gmake - found ===> gdbm-1.8.3 depends on executable: libtool - found ===> Configuring for gdbm-1.8.3 [...] checking host system type... i386-unknown-freebsdelf4.8 [...] /usr/bin/install -c -o root -g wheel -c .libs/libgdbm.a /usr/local/lib/libgdbm.a ranlib /usr/local/lib/libgdbm.a chmod 644 /usr/local/lib/libgdbm.a /usr/bin/env OBJFORMAT="elf" /sbin/ldconfig -m /usr/local/lib ---------------------------------------------------------------------- Libraries have been installed in: /usr/local/lib If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,--rpath -Wl,LIBDIR' linker flag See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- install -c -o root -g wheel -m 444 -o bin -g bin gdbm.h \ /usr/local/include/gdbm.h install -c -o root -g wheel -m 444 -o bin -g bin ./gdbm.3 \ /usr/local/man/man3/gdbm.3 install -c -o root -g wheel -m 444 -o bin -g bin ./gdbm.info \ /usr/local/info/gdbm.info ===> Generating temporary packing list ===> Compressing manual pages for gdbm-1.8.3 ===> Running ldconfig /sbin/ldconfig -m /usr/local/lib ===> Registering installation for gdbm-1.8.3 ===> Returning to build of pike72cvs-7.2.380_1 Error: shared library "gdbm.2" does not exist *** Error code 1 Stop in /usr/ports/lang/pike72cvs. *** Error code 1 Thanks for any help. Elan

2 1

Re: Problem building pike
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 28 May '03

28 May '03

>checking for mysql_real_connect in mysqlclient... yes >checking for mysql_real_query... yes >checking for mysql_fetch_lengths... yes >checking for mysql_port... yes >checking for mysql_unix_port... yes >checking if mysql_fetch_lengths() returns an uint or an ulong... unsigned long The above indicates that your mysql libraries were detected successfully. What does ldd Mysql.so say? >Thank you, > >-- >lrathle(a)teaser.fr / Henrik Grubbström (Lysator) Previous text: >2003-05-28 01:19: >Subject: Re: Problem building pike >-------------------------------------------------------------------- >Le Mercredi 28 Mai 2003 01:00, Martin Stjernholm, Roxen IS @ Pike developers >forum a écrit : > >I answer to you in private, since it's a bit long, and I have to attach a >file. > >> What does the configure output for the Mysql module say? > >Mysql $./configure --without-GTK --without-GL --without-GLUT >creating cache ./config.cache >checking for gcc... gcc >checking whether the C compiler (gcc ) works... yes >checking whether the C compiler (gcc ) is a cross-compiler... no >checking whether we are using GNU C... yes >checking whether gcc accepts -g... yes >checking if we are using TCC... no >checking for the Pike module base directory... found >checking for Mysql lib-directory... /usr/lib/mysql >Adding /usr/lib/mysql to the library search path. >checking for Mysql include-directory... /usr/include/mysql >Adding /usr/include/mysql to the include search path. >checking how to run the C preprocessor... gcc -E >checking for winsock.h... no >checking for mysql.h... yes >checking for mysql/mysql.h... yes >checking for errmsg.h... yes >checking for mysql/errmsg.h... yes >checking for bchange in -lmystrings... yes >checking Mysql version... post3.20 >checking for socket in -lsocket... no >checking for gethostbyname in -lnsl... yes >checking for pthread_self... yes >checking for _db_doprnt_ in -ldbug... no >checking for my_init in -lmysys... no >checking for compress in -lz... yes >checking for mysql_real_connect in mysqlclient... yes >checking for mysql_real_query... yes >checking for mysql_fetch_lengths... yes >checking for mysql_port... yes >checking for mysql_unix_port... yes >checking if mysql_fetch_lengths() returns an uint or an ulong... unsigned long >checking whether make sets ${MAKE}... yes >checking for the Pike base directory... found >updating cache ./config.cache >creating ./config.status >creating make_variables >creating Makefile >creating config.h >config.h is unchanged > >What's in >> modules/Mysql/config.log? > >I join config.log > >Thank you, > >-- >lrathle(a)teaser.fr > > / Brevbäraren >

5 6

Re: Problem building pike
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 28 May '03

28 May '03

> I answer to you in private, since it's a bit long, and I have to attach a > file. Sorry, but the lyskom gateway must have fooled you - you answered to the list. Not that I think it matters much. > checking for mysql_real_connect in mysqlclient... yes According to the source this successful test should be enough to define HAVE_MYSQL and hence compile in Mysql support. What does indices(Mysql); say on the interactive prompt? > I join config.log I can see that your -R/usr/lib/mysql argument isn't recognized. There's no use adding it, but it seems gcc goes on anyway. / Martin Stjernholm, Roxen IS Previous text: >2003-05-28 01:19: >Subject: Re: Problem building pike >-------------------------------------------------------------------- >Le Mercredi 28 Mai 2003 01:00, Martin Stjernholm, Roxen IS @ Pike developers >forum a écrit : > >I answer to you in private, since it's a bit long, and I have to attach a >file. > >> What does the configure output for the Mysql module say? > >Mysql $./configure --without-GTK --without-GL --without-GLUT >creating cache ./config.cache >checking for gcc... gcc >checking whether the C compiler (gcc ) works... yes >checking whether the C compiler (gcc ) is a cross-compiler... no >checking whether we are using GNU C... yes >checking whether gcc accepts -g... yes >checking if we are using TCC... no >checking for the Pike module base directory... found >checking for Mysql lib-directory... /usr/lib/mysql >Adding /usr/lib/mysql to the library search path. >checking for Mysql include-directory... /usr/include/mysql >Adding /usr/include/mysql to the include search path. >checking how to run the C preprocessor... gcc -E >checking for winsock.h... no >checking for mysql.h... yes >checking for mysql/mysql.h... yes >checking for errmsg.h... yes >checking for mysql/errmsg.h... yes >checking for bchange in -lmystrings... yes >checking Mysql version... post3.20 >checking for socket in -lsocket... no >checking for gethostbyname in -lnsl... yes >checking for pthread_self... yes >checking for _db_doprnt_ in -ldbug... no >checking for my_init in -lmysys... no >checking for compress in -lz... yes >checking for mysql_real_connect in mysqlclient... yes >checking for mysql_real_query... yes >checking for mysql_fetch_lengths... yes >checking for mysql_port... yes >checking for mysql_unix_port... yes >checking if mysql_fetch_lengths() returns an uint or an ulong... unsigned long >checking whether make sets ${MAKE}... yes >checking for the Pike base directory... found >updating cache ./config.cache >creating ./config.status >creating make_variables >creating Makefile >creating config.h >config.h is unchanged > >What's in >> modules/Mysql/config.log? > >I join config.log > >Thank you, > >-- >lrathle(a)teaser.fr > > / Brevbäraren >

2 1

Problem building pike
by Laurent Rathle 28 May '03

28 May '03

Hello, I have problem trying building Pike-v7.2.239 on Linux 2.4.21 / Mandrake 9.1 / gcc 3.2.2 / MySQL-4.0.11a. I don't have the support for mysql. Mysql libraries are in /usr/lib/mysql and headers in /usr/include/mysql. I have tried : CPPFLAGS="-I/usr/include/mysql" LDFLAGS="-L/usr/lib/mysql -R/usr/lib/mysql" ./configure --without-GTK --without-GL --without-GLUT make make install and it doesn't work. What I don't understand is that I have this : /usr/local/pike/7.2.239/lib/modules/Mysql.so after the install. Thank you, -- lrathle(a)teaser.fr

2 1

Locale.Charset.ascii
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 24 May '03

24 May '03

Locale.Charset.ascii exists in 7.4 but is gone in 7.5. Is that intentional?

4 9

Jump to page:

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