[MacPorts] #36026: gcc46 problem after ld64 upgrade
MacPorts
noreply at macports.org
Thu Sep 13 19:11:05 PDT 2012
#36026: gcc46 problem after ld64 upgrade
-------------------------+------------------------
Reporter: jwhowse4@… | Owner: jeremyhu@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.1.2
Resolution: | Keywords:
Port: ld64 |
-------------------------+------------------------
Comment (by jwhowse4@…):
Replying to [comment:34 ryandesign@…]:
> Replying to [comment:31 jwhowse4@…]:
> > I have seen several errors similar to the following.
> > {{{
> > ld: file is universal (2 slices) but does not contain a(n) x86_64
slice: /usr/lib/crt1.10.5.o for architecture x86_64
> > }}}
>
> I have too, on Mountain Lion.
>
> > This suggests to me that perhaps ld64 is mistaking Lion (10.7) for
Leopard (10.5) at least on my system.
>
> No, I don't think it suggests that. Even on Mountain Lion, there only
exists a crt1.10.5.o and a crt1.10.6.o in that directory. `lipo` confirms
that they contain both expected architectures:
>
> {{{
> $ lipo -info /usr/lib/crt1.10*
> Architectures in the fat file: /usr/lib/crt1.10.5.o are: i386 x86_64
> Architectures in the fat file: /usr/lib/crt1.10.6.o are: i386 x86_64
> }}}
>
> So the error message suggests to me that there is a problem with ld64
determining the file's architecture.
I do not know anything about Mountain Lion but on Lion there are 3 files
in /usr/lib with the prefix crt1.
{{{
lipo -info /usr/lib/crt1.*
Architectures in the fat file: /usr/lib/crt1.10.5.o are: x86_64 i386
Architectures in the fat file: /usr/lib/crt1.10.6.o are: x86_64 i386
Architectures in the fat file: /usr/lib/crt1.o are: x86_64 i386
}}}
I do not understand why the linker is looking at crt1.10.5.o rather than
crt1.o.
--
Ticket URL: <https://trac.macports.org/ticket/36026#comment:40>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list