Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#28603 closed defect (fixed)

perl5.x and Lion (10.7)

Reported by: angel@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: perl lion Cc:
Port: perl5.12 perl5.8

Description (last modified by ryandesign (Ryan Schmidt))

Seams like perl5.8 & 5.12.3 are not compiling (configure for 5.12) correctly on lion, I tried with clang & gcc and I get about the same result a compilation error with 5.8 and some obscure configuration error with 5.12.3.

I'm running Lion (10.7)

i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.9)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Apple clang version 2.0 (tags/Apple/clang-137) (based on LLVM 2.9svn)
Target: x86_64-apple-darwin11
Thread model: posix

Change History (4)

comment:1 Changed 10 years ago by ryandesign (Ryan Schmidt)

Description: modified (diff)

Lion is not released yet; we can't really help with unreleased versions of Mac OS X.

comment:2 Changed 10 years ago by dan@…

The issue with this (as far as I have debugged this.) is the way perl Configure is looking for libc.dylib.

It greps for fprintf and for some reason it's not in /usr/lib/libc.dylib. (It uses /usr/bin/nm to find the object methods)

Also if I just download stock perl tar.gz and try to configure it manually the same error occurs. So therefore I would suggest this is an issue with either perl/XCode/[Something new in Lion's setup of libc] and not directly MacPorts.

comment:3 Changed 10 years ago by jmroot (Joshua Root)

Resolution: wontfix
Status: newclosed

Reopen if this is still a problem when Lion is actually released. BTW, I'd check if your NDA allows you to post this kind of info publicly.

comment:4 Changed 10 years ago by jmroot (Joshua Root)

Resolution: wontfixfixed

Based on comment:2, r76831 should fix this.

Note: See TracTickets for help on using tickets.