Subject: Re: Short 'gnu/dist/toolchain' guide anywhere
To: Todd Vierling <tv@wasabisystems.com>
From: Markus W Kilbinger <kilbi@rad.rwth-aachen.de>
List: current-users
Date: 08/02/2001 20:25:50
>>>>> "Todd" == Todd Vierling <tv@wasabisystems.com> writes:
Todd> : I did. Seems to work, got a working toolchain in
Todd> /usr/local/bin which : always uses -L/usr/local/lib for
Todd> linking binaries (bug or feature?).
Todd> This is a `feature' of *both* `gcc' and the binutils `ld',
Todd> which I've protested on several occasions. It's unlikely to
Todd> be changed in an out-of-the-box toolchain build.
So, what is src/gnu/dist/toolchain meant for? An alternative /
replacement / more actual compared to the older in-tree stuff?
Cross-compiling? Both?
Todd> An in-tree toolchain build overrides this with just
Todd> /usr/lib, however.
How to build this?
Todd> : Anyway: When using this toolchain for compiling NetBSD
Todd> userland : /usr/local/lib/libintl.so.1 is referenced but not
Todd> found during runtime : of several binaries (e. g. grep). How
Todd> to solve this?
Todd> Nuke the version in /usr/local/lib, if possible. If not,
Todd> make sure src/lib/libintl is installed,
Several pkgsrc stuff requires/builds the pkgsrc/devel/gettext-lib
(libintl.so.1) which superseeds the system /usr/lib/libintl.so.0. Then
this odyssey began...
Todd> and build `src' with DESTDIR=/ (will set -nostdlib and other
Todd> things which should turn off this behavior).
Aah, good to know. :-)
Markus.