Re: "file is not of required architecture" error on most sample code builds on xcode 3
Re: "file is not of required architecture" error on most sample code builds on xcode 3
- Subject: Re: "file is not of required architecture" error on most sample code builds on xcode 3
- From: "Adam R. Maxwell" <email@hidden>
- Date: Sun, 11 Nov 2007 21:02:53 -0800
On Nov 11, 2007, at 6:06 AM, Alastair Houghton wrote:
On 10 Nov 2007, at 21:50, Chris Espinosa wrote:
A number of people have run into this (and, oddly, it was never
reported during the 18 months of Xcode 3 seeding).
That's probably because people are wary about using seed versions
for "real" development work; not to mention the fact that because
Xcode 3 only runs on Leopard, using it meant running a Leopard seed
and then developing code on it with an Xcode seed.
As a result, chances are that the systems on which it was installed
were clean to start with. I know I only happened across a /usr/
local/lib problem when I moved my main development machine to
Leopard, and it happened not because of Fink, but because I had
built other software that had installed libraries in /usr/local/
lib. And yes, I had been using Xcode 3 seeds on Leopard seeds prior
to that, but only really for isolated experiments.
Well, I've used Leopard daily in a "real" environment since its first
seed release, since that really is the best way to find bugs. As a
consequence, I found and reported this problem last July, and it came
back "Behaves Correctly." I sent that info to Chris offlist, and he
found the report (it went to a different group).
Some third-party package (I'm told it's fink) installs a thin set
of libraries in /usr/local/lib, and the 10.4u SDK has a symlink
that allows you to use local libs when using the SDK. IOKit tries
to link against the system's (fat) libTIFF but it grabs the (thin)
local one instead.
The solution is to clear out /usr/local/lib.
That's not a workable solution for many of us. You can also build
against the 10.5 SDK, as long as it doesn't break your app, since
ImageIO in Leopard is built in a way that keeps the linker from
searching for libpng/libtiff/libjpeg.
Or to remove the symlink. I'm not entirely convinced that this
symlink is a good idea in the first place, even if you're only
talking about the 10.5 SDK's symlink on a machine running Leopard
(or the 10.4 SDK's symlink on a machine running Tiger). It seems
unlikely that a developer would want to link against libraries in /
usr/local/lib because they won't be available on customers'
machines, and it seems equally unlikely that a framework (especially
a system framework) would want to do that.
I tried removing that symlink when I first encountered the problem,
and it didn't help. The response to my bug report indicated that the
new linker searches all -L paths, then /usr/lib and /usr/local/lib.
--
adam
_______________________________________________
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