[csw-users] symbol errors compiling using other blastwavepackages

[Lundgren, Scott]

Nope. Configure complains of not finding the mysql libraries now.
Details below. Derek when you were able to get it to compile did you use
my configure options? 

Scott Lundgren
ITS - Web Services
UNC at Charlotte
http://www.uncc.edu

bash-2.05$ env
PWD=/var/tmp/pure-ftpd-1.0.21
LD_OPTIONS=-R/opt/csw/lib -L/opt/csw/lib
CC=/opt/SUNWspro/bin/cc
MACHTYPE=sparc-sun-solaris2.9
CPPFLAGS=-I/opt/csw/include
SHELL=/bin/bash
HOSTTYPE=sparc
OSTYPE=solaris2.9
TERM=vt100
PATH=/usr/bin::.:/opt/csw/bin:/opt/csw/sparc-sun-solaris2.8/bin:/opt/SUN
Wspro/bin:/usr/ccs/bin
_=/usr/bin/env 

bash-2.05$ ./configure --prefix=/opt/csw --mandir=/opt/csw/share/man
--infodir=/opt/csw/share/info --with-openssl=/opt/csw --with-tls
--with-certfile=/opt/csw/ssl/private/pure-ftpd.pem --with-mysql=/opt/csw
--with-puredb --with-quotas --with-altlog --with-virtualchroot
<-- snip -->
checking for mysql_init in -lmysqlclient... yes
checking whether mysql clients can run... no
configure: error: Your MySQL client libraries aren't properly installed
bash-2.05$ less config.log 
<-- snip -->
configure:22400: checking for mysql_init in -lmysqlclient
configure:22430: /opt/SUNWspro/bin/cc -o conftest -g -I/opt/csw/include
-D_GNU_SOURCE=1 -I/usr/local/include -D__EXTENSIONS__=1 -D_XPG4_2=1
-I/opt/csw/include -I/opt/csw/include/mysql -I/opt/csw/mysql/include
-L/usr/local/lib -L/opt/csw/lib -L/opt/csw/lib/mysql
-L/opt/csw/mysql/lib conftest.c -lmysqlclient  -lz -lm -lcrypt
-lsendfile -lnsl -lsocket  >&5
configure:22436: $? = 0
configure:22439: test -z                         || test ! -s
conftest.err
configure:22442: $? = 0
configure:22445: test -s conftest
configure:22448: $? = 0
configure:22461: result: yes
configure:22476: checking whether mysql clients can run
configure:22502: /opt/SUNWspro/bin/cc -o conftest -g -I/opt/csw/include
-D_GNU_SOURCE=1 -I/usr/local/include -D__EXTENSIONS__=1 -D_XPG4_2=1
-I/opt/csw/include -I/opt/csw/include/
mysql -I/opt/csw/mysql/include  -L/usr/local/lib -L/opt/csw/lib
-L/opt/csw/lib/mysql -L/opt/csw/mysql/lib conftest.c -lmysqlclient -lz
-lm -lcrypt -lsendfile -lnsl -lsocket  >&5
configure:22505: $? = 0
configure:22507: ./conftest
ld.so.1: conftest: fatal: libmysqlclient.so.14: open failed: No such
file or directory
./configure: line 1: 17327 Killed                  ./conftest$ac_exeext
configure:22510: $? = 137
configure: program exited with status 137

bash-2.05$ ls -l /opt/csw/lib/mysql/libmysqlclient.so.14
lrwxrwxrwx   1 root     other         24 Feb 23 11:02
/opt/csw/lib/mysql/libmysqlclient.so.14 -> libmysqlclient.so.14.0.0


 

-----Original Message-----
From: users-bounces+selundgr=email.uncc.edu at lists.blastwave.org
[mailto:users-bounces+selundgr=email.uncc.edu at lists.blastwave.org] On
Behalf Of Derek Morr
Sent: Thursday, March 02, 2006 4:37 PM
To: questions and discussions
Subject: Re: [csw-users] symbol errors compiling using other
blastwavepackages

Lundgren, Scott wrote:
> I'm not familiar with LD_OPTIONS. When should I use LD_OPTIONS versus 
> LD_LIBRARY_PATH?

LD_LIBRARY_PATH sets the search path for the runtime linker. It's use is
generally discouraged.

> What is the difference between the -L & -R that Darin suggested
> 
> LD_OPTIONS='-R/opt/csw/lib/$ISALIST -R/opt/csw/lib -L/opt/csw/lib'
> 
> ad the -R & -R options that Derek suggested
> 
> export LD_OPTIONS="-R/opt/csw/lib -R/opt/csw/lib"

This was a typo on my part. The second R should have been an L. Sorry.

So, did it finally compile?


--
Derek Morr
Senior Systems Programmer
Academic Services & Emerging Technologies Pennsylvania State University
derekmorr at psu.edu _______________________________________________
users mailing list
users at lists.blastwave.org
https://lists.blastwave.org/mailman/listinfo/users