--dpEE41+QZ7HQEdc/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jun 11, 2005 at 11:18:22AM -0500, John D. Baker wrote:
  | On Sat, 11 Jun 2005, Idar Tollefsen wrote:
  |=20
  | > > I'm not at my Mac OS X system, but IIRC, libSystem is much like
  | > > libc. You shouldn't have to do anything special to link with it.
  | >
  | > And libstdc++. For instance, "-lstdc++" tells the linker to do some
  | > magic and link against libSystem. But, as you say, this should all
  | > happen behind the scene.
  |=20
  | In /usr/lib/, libc.dylib (as well as a number of others) is a symlink
  | to libSystem.dylib (which is a symlink to libSystem.B.dylib).  Unless
  | the linker is being told to ignore libc, or libSystem, or whatever voodo
  | Apple did to their gcc, it should have picked up the the equivalent of
  | libgen automagically.  Strange.
  |=20
  | Unfortunately, there's no consistency between releases of MacOS X as to
  | which libs are separate files and which libs are just symlinks to
  | libSystem, as the case of qt3-libs and qt3-tools illustrates (10.2 rolls
  | libresolv into libSystem and libdl is separate, while 10.3 does the
  | opposite).

Please try tnftp 20050625.

I've tested configuring, building and running it on
NetBSD 3.0_BETA, Darwin 7.9.0, and SunOS 5.9.

Luke.

--dpEE41+QZ7HQEdc/
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (NetBSD)

iD8DBQFCvQHypBhtmn8zJHIRAt66AJwJV2/zp7N8Q+ujorYwX4qGdT5KSACguZp1
J5TT3GmQ6ZFizDGIxyJh1fA=
=1G9W
-----END PGP SIGNATURE-----

--dpEE41+QZ7HQEdc/--