--tctmm6wHVGT/P6vA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

hi,

On Wed, Aug 20, 2003 at 12:28:23PM +0200, Julien T. Letessier wrote:
>=20
> Lubomir, could you give some details about the problems you've
> encounterd with GNU ld on sparc64? We at Solarpack use it exclusively
> to build our packages, and we've never encountered any problems.

corrupted libraries, unresolved symbols when they are there, problems
with linking agains 64-bit libraries, to name a few.  it was some time
ago but i don't believe it has changed that much (and i am not willing
to waste my time trying it again).

that said, if you can make it work with GNU binutils AND Solaris ld, go
for it.  99% of the software in pkgsrc links just fine with Solaris ld
(only some minor tweaking of the broken packages might be needed) but i
am strongly against using GNU binutils as the preferable toolchain for
Solaris/pkgsrc (and i believe i am not the only one who was beaten with
the problems mentioned, grant?).

> And about Solaris ld, our opinion is that pkgsrc should be made as
> independent as possible from the underlying platform tools (whose
> evolution and behavior we don't control). The good side of this is
> that packages are usually designed for a GNU tool chain, and are
> therefore much more portable if you use the same tool chain
> everywhere.

independent, yes.  GNU binutils preferable, no.


regards,

--=20
-- Lubomir Sedlacik <salo@Xtrmntr.org>                   --
--                  <salo@silcnet.org>                   --

--tctmm6wHVGT/P6vA
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE/Q1DQiwjDDlS8cmMRAiuDAJ4repcyBPdeLb0yW2+odTJiOu5ZAQCeNcfA
PYGf2R0980M9U+Gj70S6G2Q=
=eeo3
-----END PGP SIGNATURE-----

--tctmm6wHVGT/P6vA--