Well, I can get it to build by linking libgcc_s.dylib ->
libgcc_s.1.0.dylib in /usr/lib.
Runs fine too.
Is there any other way to get the linker to find this lib with some
Makefile trickery? Or should this just be listed as caveat in the README
or something?
Cheers,
Bas.
Bas Scheffers wrote:
Torben Brosten wrote:
I saw this error on 1 machine, but not on another --both the same
build etc. (1 machine about 6 months newer than the other). Couldn't
find a
Do you know if XCode was installed on one and not the other? I am really
suspecting that to be the problem as it is the only thing that would
touch libraries that I upgraded in the mean time and others with older
versions don't have this problem.
I tried GCC 3.3, but that doesn't do the trick, it's a library issue.
Also XCode 2 (working) already had GCC 4 as standard.
hopefully there's an easier way for you than a complete re-install..
I will find it, even if there has to be a switch in the Makefile to fix
it on OS X. No re-install for me!
Cheers,
Bas.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
