The only useful question in this message is:
How do I pass "-Wl,-R/usr/local/lib" to everything while
configuring and compiling MySQL?
Please don't tell me about adding LD_LIBRARY_PATH to
my profile. That's just plain dumb when you should be
able to pass "-R" to the linker.
Everything else below here is just a rant about how
inferior the MySQL configure and build process is.
I find it impossible to believe the INSTALL-SOURCE file when it
says "We use and develop the software ourselves primarily on
Sun Solaris (Versions 2.5 - 2.7) and SuSE Linux Version 7.x."
Get a stock Solaris x86 box. Install GCC and make from
sunfreeware.com like any sane administrator would do.
Get, compile and install the shared zlib libraries(let it compile
into the default /usr/local/lib "./configure --shared")
Now try to install and compile MySQL and watch it barf on
trying to find libz. I've got to add so much crap to CFLAGS, LDFLAGS
and CXXFLAGS before trying to configure MySQL that having an
automated build environment is basically useless.
The "cross-compiler" check is a real treat. Its always wrong and
you wind up having to compile c++ files with a C compiler and then
you wonder why you get unresolved symbols or other linking problems.
If you want it to be compiled by gcc write it in C, otherwise make
sure you check g++ correctly. The x86 GCC binaries on sunfreeware
are not crosscompilers, and even if they were it wouldn't matter;
I get the same problems after spending the day compiling GCC natively
on the box I'm trying to compile MySQL on.
Oh so maybe try Solaris 8... Get GCC 3.0.1 and try to build with
that and make...
gcc -DDEFAULT_CHARSET_HOME=\"/usr\" -DDATADIR=\"/home/mysql\"
-DSHAREDIR=\"/usr/share/mysql\" -DUNDEF_THREADS_HACK -DDONT_USE_RAID -I./../include
-I../include -I./.. -I.. -I.. -O3 -DDBUG_OFF -O3 -DHAVE_CURSES_H
-I/mnt/nfs/NTCSoftware/mysql/src/mysql-3.23.43/include -DHAVE_RWLOCK_T -c password.c
-fPIC -DPIC -o .libs/password.lo
Assembler: password.c
"/var/tmp/ccn6BEfI.s", line 166 : Illegal mnemonic
"/var/tmp/ccn6BEfI.s", line 166 : Syntax error
"/var/tmp/ccn6BEfI.s", line 222 : Illegal mnemonic
"/var/tmp/ccn6BEfI.s", line 222 : Syntax error
"/var/tmp/ccn6BEfI.s", line 378 : Illegal mnemonic
"/var/tmp/ccn6BEfI.s", line 378 : Syntax error
"/var/tmp/ccn6BEfI.s", line 457 : Illegal mnemonic
"/var/tmp/ccn6BEfI.s", line 457 : Syntax error
yes I purposely left out any detailed information about my machine, my OS,
what I had for breakfast this morning...
Cause I've spent the last three days hunting down answers from
google groups and it doesn't take a genius to realize that
tons of people have problems building MySQL on Solaris. And there
is always some know-it-all that thinks -L and -I will fix all your
problems.
So I highly doubt anyone would have an accurate answer for me even
if I did include details. And the answers in the INSTALL-SOURCE file
are silly. Why should I have to mess up my filesystems by putting all
sorts of crazy symbolic links everywhere or rely on people to have
LD_LIBRARY_PATH set when I should be able to just as easily pass -R
(or other options) to the compiler and linker when they are doing their
job. Then mysql would work even if I moved the binaries to a different
machine that didn't have all the messy sym-links.
I am however suggesting that people take a closer look at the
configuration stage and get it right.
Is any of this cleanup in 4.0?
So that's my rant in a nutshell.
- Jeff
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
