Are you linking against an old library binary? DVP ---- Dathan Vance Pattishall http://www.friendster.com
> -----Original Message----- > From: V. M. Brasseur [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 03, 2004 10:19 AM > To: MySQL Listserv > Subject: Undefined symbols compiling against 4.1.7 on Solaris 2.8 > > We're trying to get 4.1.7 to play nicely with our code, but something > isn't cooperating. > > First of all, the MySQL installation: Version 4.1.7, compiled from > source using GCC 3.3. The source compile is required because we need a > lot of default settings to use our own paths. This is the configure > used for the compile (some values altered here to protect the innocent): > CC=gcc CFLAGS="-O3" \ > CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" \ > ./configure --prefix=/path/to/mysql \ > --libexecdir=/path/to/mysql/bin \ > --with-mysqld-user=ouruser \ > --with-unix-socket-path=/path/to/mysql.sock --with-tcp-port=ourport \ > --without-docs --without-bench --with-extra-charsets=complex \ > --enable-thread-safe-client --enable-local-infile \ > --localstatedir=/path/to/mysql/data \ > --with-prefix=/path/to/mysql \ > --with-low-memory --enable-assembler --disable-shared > > It appears to function well on its own. However, when attempting to > compile a program which requires libmysqlclient.a... > > compiling -o progname /path/to/progname.c > Undefined first referenced > symbol in file > __floatdisf > /path/to/mysql/lib/libmysqlclient.a(libmysql.o) > __floatdidf > /path/to/mysql/lib/libmysqlclient.a(libmysql.o) > __cmpdi2 > /path/to/mysql/lib/libmysqlclient.a(libmysql.o) > ld: fatal: Symbol referencing errors. No output written to progname > compile:error=256,command=compiling -o progname /path/to/progname.c > > It's worth noting that we are only experiencing this problem on Solaris > 2.8. Another 4.1.7 installation on OSF1 5.1 is chugging along nicely > with no complaints. > > Google contains many references to these undefined symbols, encountered > mostly when compiling other products. Yet none of those references > contain an actual SOLUTION to the problem. > > Could someone out there with a bit more ld/gcc/C API experience than I > have (which is not setting the bar high, I assure you) lend a hand > dispersing these clouds? > > Many thanks, > > --V > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
