On Thursday, August 30, 2001, at 01:58 AM, Matt Patterson wrote:
> On 28/8/01 at 11:15 pm, [EMAIL PROTECTED] wrote:
>
>> Anyways, to compile jpeg-6b, just:
>>
>> % cd /path/to/jpeg-6b-source
>> % cp /usr/libexec/config.* .
>> % ./configure
>> % make
>>
>> The second line is the trick; this overwrites config.guess and
>> config.sub with versions that know about MacOSX (darwin).
>
> Can I assume from this that to compile other things whose configure
> scripts
> don't know about darwin I can do this, and if that's the only problem
> I'll be
> fine...
>
> (I'm thinking of the Gnome libXML and libXSLT here...)
I don't know first-hand about Gnome libXML and libXSLT, but the config.*
trick is probably one that will get you through most. There are some
things that special case for NeXTStep/OpenStep code, but don't know about
darwin directly, so you have to modify the code to do it the
NeXTStep/OpenStep way (e.g., the dynamic loader stuff in Apache has needed
this fix).
I've seen a few differences among pure gcc compilers and the MacOSX cc
compiler, as well as a subtle difference with the use of "sed" in a script
used as part of the build process (or was it "awk"; I forget). Some are
easy to find, some are not. But that is just part of the game as no
unix-like system is exactly like another, and you just have to hope that
the code is either generic enough or has been special cased close enough
to work.
Mailing lists (and archives) are often a good source of this information
and we like to share our experiences and successes with others.
--------------------------------------------------------------------------
Edward Moy
Apple Computer, Inc.
[EMAIL PROTECTED]
(This message is from me as a reader of this list, and not a statement
from Apple.)
