Front page | perl.perl5.porters |
Postings from January 2012
On Wed, Jan 25, 2012 at 11:50:04AM -0600, David Mertens wrote: > Since nobody has raised this yet, I wonder what Apple's copy of Perl looks > like. I know, for example, that Apple's copy of Python is considered by > that community to be broken. I didn't even try using it myself: I prefer to > not mess with my system perl, so I promptly installed perlbrew. "Sane", was my understanding. I can't speak personally, as I tend to leave it alone, and use my own, or macports. Clearly people use it for their own projects, because: About the biggest unfortunate issue was when Apple's XCode 4 inadvertently broke compile XS modules on Snow Leopard. The issue being that Apple's perl is configured as a fat binary, and to build extensions as fat binaries: $ cd /System/Library/Perl/5.10.0/darwin-thread-multi-2level/auto/Fcntl/ $ file Fcntl.bundle Fcntl.bundle: Mach-O universal binary with 3 architectures Fcntl.bundle (for architecture x86_64): Mach-O 64-bit bundle x86_64 Fcntl.bundle (for architecture i386): Mach-O bundle i386 Fcntl.bundle (for architecture ppc7400): Mach-O bundle ppc Only Apple removed the ppc assembler from XCode 4, I infer because Lion doesn't support ppc, even under emulation. Which makes attempts to build fat binaries for it fail. The only other problem I can remember was when an Apple security upgrade supplied a newer IO.bundle for 1.26, which broke end user machines where they had self-upgraded IO to 1.27, because Apple only shipped the changed binary, not the IO.pm which loads it. Which I tend to think is not *entirely* Apple's fault here, because if one has been going behind the back of the OS and its package manager, one isn't exactly playing fair. When sudo says "With great power comes great responsibility" it means it. Nicholas ClarkThread Previous | Thread Next