On Aug 19, 2004, at 1:27 PM, Benjamin Adair wrote:
I used CPAN to update my DBI::DBD and DBD::mysql modules no problem on my client machines. I get something totally bogus (-arch i386!? HAH) on the servers, though. I've dug some and it seems that the mysql_config utility is to blame. For some reason the existing install that comes with OS X Server is supplying the garbage. If I run /usr/local/mysql/bin/mysql_config I see the same options that were used when it compiled on my client machines.
Okay, if I follow you correctly, you now have *both* the pre-installed MySQL (where it may be), and a newly installed MySQL in /usr/local/mysql, and you want DBD::mysql to use the new one. Is that right?
Well, DBD::mysql will use the first mysql_config it finds, which is apparently the pre-installed one. The simplest thing I can think of doing is just deleting or renaming the pre-installed mysql_config; since you've installed your new MySQL in the default location, DBD::mysql should then be able to find it.
Do I need to compile this bad boy manually and specify these options myself to get it installed? Is there a way to do it via CPAN? I guess my point is that I would like to find out if there's a 'good'/'right' way to do this.
If you need to pass options to Makefile.PL, you can do so through the CPAN shell with the 'look' command. Enter 'look Module::Name' at the CPAN shell prompt, and it will download the latest version, unzip it, and open up a command shell in the build directory. Then, run 'perl Makefile.PL --whatever'.
Once Makefile.PL is finished doing its thing, you can finish it off manually if you want, with 'make; make test; make install'. Or, you can exit from the command shell and use 'install Module::Name' at the CPAN shell.
sherm--
