Once I actually read some of the documentation, going through the 
CPAN/mysql/configure.pl thing wasn't too bad. But now I'm in some kind of Mac 
architecture hell.

I ran apache on the newly written httpd.conf (biomart 0.6, Leopard with 
presumably pretty new apache and stuff) and started getting errors like this:

Can't load 
'/sw/lib/perl5/5.8.6/darwin-thread-multi-2level/auto/XML/Parser/Expat/Expat.bundle'
 for module XML::Parser::Expat: 
dlopen(/sw/lib/perl5/5.8.6/darwin-thread-multi-2level/auto/XML/Parser/Expat/Expat.bundle,
 1): no suitable image found.  Did 
find:\n\t/sw/lib/perl5/5.8.6/darwin-thread-multi-2level/auto/XML/Parser/Expat/Expat.bundle:
 mach-o, but wrong architecture at 
/System/Library/Perl/5.8.8/darwin-thread-multi-2level/DynaLoader.pm line 230.\n 
at /sw/lib/perl5/5.8.6/darwin-thread-multi-2level/XML/Parser.pm line 
14\nCompilation failed in require at 
/sw/lib/perl5/5.8.6/darwin-thread-multi-2level/XML/Parser.pm line 14.

The actual error is about 3 times that long. The error first occurred with 
DBD::mysql. I went on the web and saw that you can get errors like this due to 
compiling "bundles" (whatever those are) for the wrong Mac architecture. So I 
set my ARCHFLAGS variable and re-made DBD::mysql. Which amazingly worked, but 
then I got an error on another module's bundle. And of course I installed 
probably a couple dozen modules to get Biomart going.

Questions:

1) Is the best way to fix this to recompile every module I had installed, using 
a more expansive ARCHFLAGS?
1a) Will compiling with more ARCHFLAGS screw up other aspects of my mac? (I'm 
installing this in the system library, so that the www user can access them, 
not just my user.)
2) Would recompiling mod_perl (scary!) and/or apache (scarier!) magically fix 
the problem I'm getting with each Perl module?
2a) Will recompiling apache screw up everything else I want to do on this box 
(my laptop!)?
3) HELP!

-Amir Karger

Reply via email to