RE: DBD::mysql make fails on RHEL 4 IA64 w/MySQL 5.1.24
"Peter Wood" <[email protected]> Wed, 27 Aug 2008 09:40:49 -0400
| Newsgroups | gmane.comp.db.mysql.perl |
|---|---|
| Message-ID | <[email protected]> |
Hi all, I've discovered the problem, and it's totally unrelated to DBD::mysql. Turns out I was confused about what architecture I was running on and which MySQL packages to download. We have an Intel Xeon which is x86_64. However, when I went to download the MySQL devel package, I didn't see x86_64, just AMD64. I thought IA64 looked like the closest thing, so that's what I installed. Whoops! I now realize that AMD64 works on both AMD64 and Intel x86_64, though I have to say that the package labeling could be a bit clearer. Sorry for the confusion! Peter -----Original Message----- From: Peter Wood Sent: Tuesday, August 26, 2008 2:45 PM To: '[email protected]' Subject: DBD::mysql make fails on RHEL 4 IA64 w/MySQL 5.1.24 Greetings, I'm trying to compile DBD::mysql on a server with the following specs: * 64-bit Intel architecture * Red Hat Enterprise Linux ES release 4 (Nahant Update 6) * MySQL community server 5.1.24 for rhel4 ia64, installed via RPM from MySQL.com * Perl 5.8.5 * DBD::mysql 4.008 I run perl Makefile.PL with default settings, then make. Make then dies. Here is a transcript of my "make" session: # make cp lib/DBD/mysql.pm blib/lib/DBD/mysql.pm cp lib/DBD/mysql/GetInfo.pm blib/lib/DBD/mysql/GetInfo.pm cp lib/DBD/mysql/INSTALL.pod blib/lib/DBD/mysql/INSTALL.pod cp lib/Bundle/DBD/mysql.pm blib/lib/Bundle/DBD/mysql.pm gcc -c -I/usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/auto/DBI -I/usr/include/mysql -g -no-ftz -no-prefetch -DUNIV_LINUX -g -D_REENTRANT -D_GNU_SOURCE -DDEBUGGING -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -O2 -g -pipe -m64 -DVERSION=\"4.008\" -DXS_VERSION=\"4.008\" -fPIC "-I/usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi/CORE" dbdimp.c gcc: unrecognized option `-no-ftz' gcc: unrecognized option `-no-prefetch' dbdimp.c: In function `alloc_param': dbdimp.c:112: warning: comparison is always false due to limited range of data type dbdimp.c: In function `alloc_bind': dbdimp.c:130: warning: comparison is always false due to limited range of data type dbdimp.c: In function `alloc_fbind': dbdimp.c:146: warning: comparison is always false due to limited range of data type dbdimp.c: In function `alloc_fbuffer': dbdimp.c:161: warning: comparison is always false due to limited range of data type /usr/bin/perl -p -e "s/~DRIVER~/mysql/g" /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/auto/DBI/Dr iver.xst > mysql.xsi /usr/bin/perl /usr/lib/perl5/5.8.5/ExtUtils/xsubpp -typemap /usr/lib/perl5/5.8.5/ExtUtils/typemap mysql.xs > mysql.xsc && mv mysql.xsc mysql.c Warning: duplicate function definition 'do' detected in mysql.xs, line 225 Warning: duplicate function definition 'rows' detected in mysql.xs, line 650 gcc -c -I/usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/auto/DBI -I/usr/include/mysql -g -no-ftz -no-prefetch -DUNIV_LINUX -g -D_REENTRANT -D_GNU_SOURCE -DDEBUGGING -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -O2 -g -pipe -m64 -DVERSION=\"4.008\" -DXS_VERSION=\"4.008\" -fPIC "-I/usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi/CORE" mysql.c gcc: unrecognized option `-no-ftz' gcc: unrecognized option `-no-prefetch' mysql.xs: In function `XS_DBD__mysql__db_do': mysql.xs:330: warning: comparison is always false due to limited range of data type mysql.xs:331: warning: comparison is always false due to limited range of data type Running Mkbootstrap for DBD::mysql () chmod 644 mysql.bs rm -f blib/arch/auto/DBD/mysql/mysql.so /usr/bin/perl myld gcc -shared dbdimp.o mysql.o -o blib/arch/auto/DBD/mysql/mysql.so -L/usr/lib/mysql -lmysqlclient -lz -lcrypt -lnsl -lm /usr/lib/mysql/libmysqlclient.a: could not read symbols: Bad value collect2: ld returned 1 exit status make: *** [blib/arch/auto/DBD/mysql/mysql.so] Error 1 Any ideas as to what could be causing this? I did check the mailing list and saw other people with the "bad value" error, but with different symptoms leading up to it. Thanks, Peter -- MySQL Perl Mailing List For list archives: http://lists.mysql.com/perl To unsubscribe: http://lists.mysql.com/[email protected]