I've burned two solid days on this now, and rather than shoot myself I think it's time to ask for help.
I finally acquiesced and ordered Jaguar for my ti/800. I do apache / mod_perl development, and I was using my mac very happily under 10.1.5 for all my coding - apache and mod_perl built from source, emacs, mysql, Perl... all the usual good stuff. It was developer's heaven. Trying to get this system working in 10.2 has been a nightmare, and it seems to have a lot to do with Perl. I did a clean install of Jaguar, and carefully followed the instructions at <http://developer.apple.com/internet/macosx/perl.html> to do a clean 5.8 install to replace the 5.6.0 that inexplicably ships with Jaguar. I then updated the Fink XS modules as described at <http:[EMAIL PROTECTED]/msg02447.html> so they'd work with 5.8.0. So far, so good. Then I built Apache 1.3.27 and mod_perl 1.27 from source using the same configs I used to build them under 10.1.5 (sources in /opt/PACKAGE/VERSION) mod_perl: perl Makefile.PL APACHE_SRC=/opt/apache/1.3.27/src/apache_1.3.27/src \ NO_HTTPD=1 USE_APACI=1 PREP_HTTPD=1 EVERYTHING=1 make all install Apache: ./configure --with-layout=Apache --prefix=/opt/apache/1.3.27/ \ --enable-module=rewrite --enable-module=speling --enable-module=expires \ --enable-module=unique_id --enable-module=info --enable-module=log_agent \ --enable-module=log_referer --enable-module=usertrack \ --enable-module=proxy \ --enable-module=userdir --enable-module=so --enable-module=most \ --activate-module=src/modules/perl/libperl.a --enable-shared=max \ --enable-shared=perl --without-execstrip make make install This all worked fine and I got a nice executable I could start, except that it would crash immediately. Nothing in the error logs. I ran it under gdb and got this: (many of this line:) Reading symbols for shared libraries . done Program received signal EXC_BAD_ACCESS, Could not access memory. 0x003aab8c in S_hv_fetch_flags () And on subsequent tries: Program received signal EXC_BAD_ACCESS, Could not access memory. 0x003b7220 in Perl_sv_upgrade () If I commented out the load of the mod_perl DSO in httpd.conf, apache worked fine. I googled like crazy but couldn't come up with much matching those errors, and concluded that it was some deep-down Perl voodoo and bad mojo with 5.8.0 and a million variables I had no idea about, and decided to scrap it and start over and avoid 5.8.0 this time. It felt like a failing, but I have to get back to work. So I did a clean reinstall of Jaguar and started over, but skipped the Perl 5.8.0 upgrade - or tried to. Fink went in fine, Apache and mod_perl went in fine with 5.6.0 and the same config/build process used above, mod_perl worked fine, everything was groovy until I tried to use CPAN to add back in the support modules I needed for my mod_perl apps. You don't get very far in CPAN.pm before it tries to blast 5.8.0 down your throat. It fails to install because it only passes 99.70% of the tests, and that blocks everything else. Hoping it was just a quick dependency check, I suspended the CPAN process and did "make install" myself, which installed it, but then, surprise surprise, CPAN broke down again and 5.8.0 became the default system Perl. Fink broke again, and I've got no idea what will happen to the mod_perl I built with 5.6.0. Looks like I'm starting over again, and this time I guess I'll have to avoid both the 5.8.0 upgrade AND CPAN, and build my modules by hand so they don't try to install 5.8.0 on me. Does anybody have any idea what these errors might be about? Program received signal EXC_BAD_ACCESS, Could not access memory. 0x003aab8c in S_hv_fetch_flags () Program received signal EXC_BAD_ACCESS, Could not access memory. 0x003b7220 in Perl_sv_upgrade () Does anybody have a Jaguar / Perl 5.8.0 / Apache 1.3.27 / mod_perl 1.27 configuration working? Or any clues about what the above errors might be related to? My preference would be to have 5.8.0 running in this setup, but if it's killing mod_perl under OSX I can't have it. I wish CPAN was a little less aggressive about trying to force-feed me 5.8.0, too, but that's a different rant. Any tips/ideas/dope-slaps welcome. -- Steve Linberg, Chief Goblin Silicon Goblin Technologies http://silicongoblin.com Be kind. Remember, everyone you meet is fighting a hard battle.
