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@teaser.fr
/ Brevbäraren
Le Mercredi 28 Mai 2003 01:40, Martin Stjernholm, Roxen IS @ Pike developers forum a écrit :
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?
$pike Pike v7.2 release 239 running Hilfe v2.0 (Incremental Pike Frontend)
indices(Mysql);
-:1:Bad argument 1 to indices(). Expected string|array|mapping|multiset|object|program|function
I've tried like this, giving mysql as a program argument :
indices(mysql);
-:1:'mysql' undefined.
pike-devel@lists.lysator.liu.se