what's going on: libstdcxx, ld64, gcc, etc.?

[Frank Schima]

On Sep 17, 2012, at 9:52 AM, Murray Eisenberg <murrayeisenberg at gmail.com> wrote:

> On Sep 16, 2012, at 4:31 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
> 
>> 
>> On Sep 16, 2012, at 10:01, Murray Eisenberg wrote:
>> 
>>> I posted a ticket that libstdcxx would not build. The ticket was closed with "duplicate" status and pointer to #36026.
>>> 
>>> But #36026 refers to gcc46 problem after ld64 upgrade. 
>>> 
>>> I just successfully upgraded ld64. Next tried to install cc46. That bombs out because it tries to build first libstdcxx.
>>> 
>>> So things seem to have come full-circle, and I quite confused about what's happening here.
>> 
>> In some situations the ld64 port builds improperly, resulting in an ld program that does not work. This ld program is then used to try to build all sorts of other ports, including libstdcxx and gcc46 and in fact most other ports you might try to build, if you already have the ld64 port installed, resulting in problems building those other ports (and even software built outside of MacPorts, if /opt/local/bin is in your path, which it usually is). It all comes back to ld64, which is where the fix is needed. I have adjusted the title of #36026 to make this clearer. Please monitor #36026 for the eventual resolution of this issue.
> 
> The latest ticket post about #36026 is "[97801]: ld64 Possible solution to #36026…?" That shows what would appear to be a new revision 3 for ld64 version 133.3. 
> 
> But the copy of ld64 that's currently active on my system is already: ld64 @133.3_3+llvm30 (active). And things like libstdcxx and hence gcc45 still won't build.
> 
> Am I misreading either the information in #97801 or in the report from 'sudo port info ld54'?

I'm far from an expert on this, but I would suggest rebuilding ld64 with the llvm31 variant since that is now the default. 


-Frank