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: Philip Hölzenspies <email@hidden>
- Date: Tue, 22 Apr 2008 17:40:10 +0100
On Apr 22, 2008, at 5:31 PM, Peter O'Gorman wrote:
Philip Hölzenspies wrote:
$ ld -r -o linked.o libMyListMod.so libMyListTree.so
ld: warning -arch not specified
ld: warning in libMyListMod.so, file is not of required architecture
ld: warning in libMyListTree.so, file is not of required architecture
You are trying to create a reloadable object file from 2 shared
libraries? Don't do that, you will just get an empty object file.
I guess I'm going to have to start a new topic or these
miscommunications will never ever be eliminated from the thread, right?
This was an over-reduced example, but whether I would want to do this
or not, the error should DEFINATELY NOT BE that the files is NOT OF
REQUIRED ARCHITECTURE.
Is there any defacto way to get everyone's attention on the ACTUAL
problem?
I'll go again:
$ ld -r -o foobar.o foo.o bar.o X.so
ld: warning -arch not specified
ld: warning in libX.so, file is not of required architecture
(Do I have to go and repaste the output of lipo and file applied to
libX.so that both state it is thin an of x86, or do I have to
explicitly include the execution of ld WITH the -arch x86 flag?) _______________________________________________
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