Hi!
I tried compiling mysql++-2.1.1 with CC 5.3 and got the following link
errors:
make[1]: Entering directory `/users/a24053/sql/mysql++-2.1.1/examples'
CC -o resetdb resetdb_resetdb.o -L/usr/local/mysql/lib/mysql -L.
-lnsl -lsocket -L../lib -lmysqlpp_util -lmysqlclient -lmysqlpp -lz
Undefined first referenced
symbol in file
__type_1 mysqlpp::ColData_Tmpl<mysqlpp::const_string>::conv<long
long>(__type_1)const ./libmysqlpp_util.a(util_util.o)
__type_1
mysqlpp::ColData_Tmpl<mysqlpp::const_string>::conv<double>(__type_1)cons
t ./libmysqlpp_util.a(util_util.o)
ld: fatal: Symbol referencing errors. No output written to resetdb
make[1]: *** [resetdb] Error 1
Can you please let me know what can be the reason and how to solve it??
Regards,
Manik Gupta
-----Original Message-----
From: Warren Young [mailto:mysqlpp@stripped]
Sent: Saturday, October 07, 2006 1:09 AM
To: MySQL++ Mailing List
Subject: Re: Problem in building mysql++-2.0.7 examples on Solaris 8
using CC 5.3
Gupta Manik-a24141 wrote:
>
> I am trying to build the mysql++-2.0.7 examples on Solaris 8 using CC
> 5.3
I would first suggest trying a newer compiler, or switching to GCC.
MySQL++ has a way of pushing compilers to their limits: there are many
C++ compilers that claim to comply with the standard, but which do not
in fact support the entire language. MySQL++ uses more features in the
language than most other C++ libraries.
You might also install all of the current autotools on your system
(autoconf, automake, libtool...), and then run the bootstrap script.
It's possible -- though unlikely -- that there are linkage fixes in
these tools that aren't in the distributed versions of MySQL++ that are
in current autotools.
Finally, and this is a long shot, I'd try MySQL++ 2.1. If anything,
though, this is a step backwards relative to the linkage issues. The
only reason it might improve things is that the new build system is a
lot less clever than the old one, so it might work by virtue of not
pushing your development tools in a direction they don't want to go.
That said, moving to MySQL++ 2.1 is a good idea anyway, because we're
just not going back to the autotools. Bakefile solves a real problem
for us, so if I make any change here at all, it's to another similar
tool. I'm not going to regress on this front.
--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe:
http://lists.mysql.com/plusplus?unsub=1
