I still have to say that i am unhappy because libjpeg is not the
only one that i have to bake a fat binary of - after lipo-ing together
a universal libjpeg, the build fails with libgif causing the same
problem (and i am already expecting more work-causing trouble
of the same kind coming my way from the rest of the occupants
of /usr/local/lib). Is this really the way it's supposed to be?
No. It's a problem that's been caused by the combination of the new
linker, the 10.4 version of ImageIO, the fact that you had already
built copies of libjpeg et al. on your system and the fact that there
is a symlink in the SDK.
IMO the symlink in the SDK is a mistake, so the best fix is
That way, your 10.4u SDK really does represent a clean 10.4 system,
which (I think) is what most people want. It's certainly what *I* want.
The reason why i am complaining so much is that i somehow
expected a new, clean, freshly installed system to be equipped
with the standard stuff needed to be able to cross-develop for
(not so much) older systems.
It is. In order to have this problem, you need to have built copies
of these libraries yourself (maybe as part of installing some Open
Source software).
