#28628 closed defect (invalid)
perl5.8 fails to install because of /usr/local/lib/libstdc++.6.dylib
Reported by: | naromero@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.2 |
Keywords: | Cc: | ghosthound, ryandesign (Ryan Carsten Schmidt) | |
Port: | perl5.8 |
Description
I am attaching a log, but what I don't understand is why this port is using the Apple compiler in /usr/bin/ (gcc 4.2) rather than the compiler from macports (gcc 4.5)
Attachments (1)
Change History (7)
Changed 14 years ago by naromero@…
comment:1 Changed 14 years ago by naromero@…
Cc: | naromero@… added |
---|
comment:3 Changed 14 years ago by naromero@…
This is similar to this ticket, #25707
But both version (i386 and x86_64) version of the library are available:
/usr/local/lib/libstdc++.6.dylib
/usr/local/lib/x86_64/libstdc++.6.dylib
This directory structure may be because of the Leopard to Snow Leopard upgrade, not sure.
In any case, a variant using newer versions of the GNU compiler. Would be welcomed.
comment:4 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ricci@… ryandesign@… added; naromero@… removed |
---|---|
Port: | perl5.8 added |
Resolution: | → invalid |
Status: | new → closed |
Summary: | perl5.8 fails to install because of i386 vs. x86_64 issue → perl5.8 fails to install because of /usr/local/lib/libstdc++.6.dylib |
Replying to naromero@…:
I am attaching a log
The relevant line is:
ld: in /usr/local/lib/libstdc++.6.dylib, file was built for i386 which is not the architecture being linked (x86_64)
This library is interfering with the build. Remove it and anything else in /usr/local. Having things installed in /usr/local is not supported while using MacPorts.
but what I don't understand is why this port is using the Apple compiler in /usr/bin/ (gcc 4.2) rather than the compiler from macports (gcc 4.5)
Most ports use Apple's Xcode gcc compiler in /usr/bin. This is normal. Only ports that specifically need a MacPorts gcc compiler do so.
comment:5 Changed 14 years ago by naromero@…
This should not be necessary IMO. In any case, I got one of the other perl5 variants to work.
sudo port install perl5 +perl5_12
The problems seems specific to perl5.8
comment:6 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Software installed in /usr/local is a frequent cause of port build failures, and we do not have the time to support that, sorry.
Cc Me!