Bug #36827 | running make on OS X server 10.3.9 yields duplicate function definitions, errors | ||
---|---|---|---|
Submitted: | 20 May 2008 18:57 | Modified: | 22 Nov 2008 9:34 |
Reporter: | Lillian Frisch | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | Connectors: DBD::mysql ( Perl ) | Severity: | S2 (Serious) |
Version: | 4.007 | OS: | MacOS (10.3.9 server) |
Assigned to: | CPU Architecture: | Any | |
Tags: | dbd, OS X Server, perl |
[20 May 2008 18:57]
Lillian Frisch
[9 Jun 2008 19:34]
Sveta Smirnova
Thank you for the report. Please try with current version of DBD::mysql 4.007 and inform us about results. Also, please, try not wit custom, but mysql_config settings and without modification of Makefile.
[4 Jul 2008 19:44]
Lillian Frisch
Thanks for your reply. I ran DBD-mysql-4.007 without the extras when executing 'perl Makefile.PL'. Here are the results: ------------------------------ llfrisch$ perl Makefile.PL PLEASE NOTE: For 'make test' to run properly, you must ensure that the database user 'llfrisch' can connect to your MySQL server and has the proper privileges that these tests require such as 'drop table', 'create table', 'drop procedure', 'create procedure' as well as others. mysql> grant all privileges on test.* to 'llfrisch'@'localhost' identified by 's3kr1t'; You can also optionally set the user to run 'make test' with: perl Makefile.pl --testuser=username I will use the following settings for compiling and testing: cflags (mysql_config) = -I/usr/include/mysql -fno-omit-frame-pointer -arch i386 -arch ppc -pipe embedded (mysql_config) = libs (mysql_config) = -arch i386 -arch ppc -pipe -L/usr/lib/mysql -lmysqlclient -lz -lm mysql_config (guessed ) = mysql_config nocatchstderr (default ) = 0 nofoundrows (default ) = 0 ssl (guessed ) = 0 testdb (default ) = test testhost (default ) = testpassword (default ) = testsocket (default ) = Use of uninitialized value in printf at Makefile.PL line 171, <PIPE> line 93. testuser ( ) = llfrisch To change these settings, see 'perl Makefile.PL --help' and 'perldoc INSTALL'. Checking if your kit is complete... Looks good Unrecognized argument in LIBS ignored: '-arch' Unrecognized argument in LIBS ignored: 'i386' Unrecognized argument in LIBS ignored: '-arch' Unrecognized argument in LIBS ignored: 'ppc' Unrecognized argument in LIBS ignored: '-pipe' Using DBI 1.605 (for perl 5.008008 on darwin-thread-multi-2level) installed in /usr/local/lib/perl5/site_perl/5.8.8/darwin-thread-multi-2level/auto/DBI/ Writing Makefile for DBD::mysql llfrisch$ 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 cc -c -I/usr/local/lib/perl5/site_perl/5.8.8/darwin-thread-multi-2level/auto/DBI -I/usr/include/mysql -fno-omit-frame-pointer -arch i386 -arch ppc -pipe -DDBD_MYSQL_INSERT_ID_IS_GOOD -g -fno-common -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -pipe -I/usr/local/include -Os -DVERSION=\"4.007\" -DXS_VERSION=\"4.007\" "-I/usr/local/lib/perl5/5.8.8/darwin-thread-multi-2level/CORE" dbdimp.c cc: cannot read specs file for arch `i386' make: *** [dbdimp.o] Error 1 ------------------------------------ So, for some reason DBD seems to get hung on the i386 flag while executing make, which shouldn't even be an issue on OS X. I wrote the cflags to try to get around that, but when I did so with 4.007 I received a horrendously long error list upon doing make (I can show you it if you like). The process did not get hung up on i386, but it did not do much better. So, to replicate: gunzip < DBD-mysql-4.007.tar.gz | tar xvf - cd DBD-myql-4.007 perl Makefile.PL make Thanks for the help so far.
[22 Oct 2008 9:34]
Sveta Smirnova
Thank you for the feedback. Please try with current version 4.009 and if problem still exists try to set RC_ARCHS=ppc in your environment before compiling.
[23 Nov 2008 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".