On 2/22/2000 at 3:46 PM, lowrey@mailbag.com (Jefferson R. Lowrey) wrote: > OS X Server (and I must admit I don't have 1.2 yet) comes with plain > old Perl, not MacPerl at all. It should be possible to run MacPerl in > MacOS.app (Classic/bluebox/your name of choice), but there'd be no > reason to. I also don't have 1.2 yet, but through 1.1 at least, be aware that the shipped version of Config.pm is either broken, or from some mythical rhapsody-intel release. It becomes a problem when you try to build a module involving any XS code -- the resulting modules are generated for i386, apparently, and the module's tests then quickly run aground. The fix is to take /System/Library/Perl/rhapsody/Config.pm, and wipe out all instances of the string "-arch i386 -arc ppc". That's from memory, so the string may be very slightly different, but it'll be clear enough when you're in there. Building a new version of perl should also fix it, of course. Aside from this little peculiarity, I've been very happy with perl under OSXS. -nat # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org