Re: thin linking: "file is not of required architecture"
Re: thin linking: "file is not of required architecture"
- Subject: Re: thin linking: "file is not of required architecture"
- From: Greg Guerin <email@hidden>
- Date: Wed, 23 Apr 2008 14:42:21 -0700
Peter O'Gorman wrote:
>Mentioning that I installed it is not a violation of the NDA, is it?
Seems unlikely.
>If you look at the z.o that is created when the "input files" are two
>shared libraries, you will see that it is empty (just the mach-o header
>etc, no symbols) because shared libraries are not a type that can be
>included in an MH_OBJECT file. I will report this as a bug .. 5884356.
I agree: it's a bug. It occurs with Xcode 3.0 tools, too.
Nevertheless, my questions remain.
The OP's lengthy 'gcc' command-line simply shows the command-line. There
are no error messages, warning messages, or any indication of its
ostensibly problematic outcome . Nor does the OP ever state what problem
the 'gcc' command-line actually exhibits: failure to compile, failure to
link, etc.
Furthermore, the 'gcc' command-line appears unrelated to the OP's
originally stated problem with 'ld -r'. AFAICT, none of the 'gcc' options
appears to lead to an 'ld -r' as part of the build procedure (i.e. 'gcc -v
...'), nor is there an explanation of how one is related to the other. I
see two points, with a lot of words apparently trying to connect them, but
I've seen nothing yet that actually connects the points.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden