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: Alastair Houghton <email@hidden>
- Date: Thu, 10 Apr 2008 13:33:08 +0100
On 10 Apr 2008, at 13:30, Philip Hölzenspies wrote:
This might be a case of an over-isolated example. It comes from
trying to link a binary. It would be too much fuss to give the
entire example, but the error came from a command like:
$ ld -arch i386 -o application lib1.so lib2.so lib3.so foo.o bar.o
and the errors where about the .so files. If you look closely, btw,
you see that ld just gives *warnings*. It's only when linking a
binary (actually, anything without the -r option) that this results
in a bunch of "symbol XXX not found" errors (where the symbols are
in the so files that ld can't properly determine the architecture
for).
Mind you, all the so files I mention here were compiled with this
exact same installation, i.e. with the same gcc/ld that fails for my
binary.
What does it say if you do
ld -arch i386 -o application foo.o bar.o lib1.so lib2.so lib3.so
instead? i.e. write the object files first, then the libraries, not
the other way around.
Kind regards,
Alastair.
--
http://alastairs-place.net
_______________________________________________
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