-----BEGIN PGP SIGNED MESSAGE-----
On Fri, 18 Jul 2003, Bernhard Graf wrote:
> to build the 4.x MySQL-RPM (currently 4.0.13) I started with the current
> SuSE-8.2 mysql.spec (3.23.55), which is quited similar to the originaL
Surprise, as I used the MySQL spec file as a template to create the
initial SuSE RPMs :)
(I used to work for SuSE before)
What's wrong with using the "official" 4.0 MySQL RPMs?
> With Google's help I was able to solve the first and often reported
> linker problems, like
> : undefined reference to `operator new(unsigned)'
> : undefined reference to `operator delete(void*)'
> ../libmysqld.a(field.o)(.gnu.linkonce.d._ZTV9Field_str+0x10): undefined
> reference to `__cxa_pure_virtual'
> by setting enironment variables
> export CXX='gcc -O3'
> export LDFLAGS='-lstdc++'
> in the SPEC file's BuildMySQL routine.
The latter should not be necessary. Try to aviod linking against libstdc++
when compiling MySQL, if possible - the manual has some more info on that
> This causes the linker to link with libstdc++ and libgcc_s.
> Because only shared versions of these libs exist (*.so but no *.a), it
> seems impossible now to build a statically linked mysql-binary.
> So far I'm able to create a dynamicly linked mysql binary, by removing
> configure arguments
> --disable-shared --with-mysqld-ldflags='-all-static'
> Any help how to link it staticly is much appreciated.
> OS: SuSE Linux 8.2
> Compiler gcc 3.3 final (ftp://ftp.suse.com/pub/projects/gcc/8.2/)
I just rebuilt the 4.0.14 SRPM on my SuSE Linux 8.2 box with gcc 3.3
final. The server binary is statically linked, as expected. Please have a
look at the 4.0 spec file for more info.
Lenz Grimmer <lenz@stripped>
Senior Production Engineer
MySQL GmbH, http://www.mysql.de/
For technical support contracts, visit https://order.mysql.com/?ref=mlgr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/
-----END PGP SIGNATURE-----