On Thu, 2 Aug 2001, Markus W Kilbinger wrote:

:     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?

Those sources are actually used by the in-tree build.

The `dist' directories (src/dist, src/crypto/dist, src/gnu/dist) contain the
unmodified directory structure from a "dist"ribution of each package, which
is then used by BSD makefiles elsewhere; here, in src/gnu/usr.bin/gcc (not
yet turned on by default).

Also, in the particular case of src/gnu/dist/toolchain, this tree provides a
toolchain which can be broken out and used separately -- either to generate
a patch diffball to use in a gcc/binutils pkgsrc package, or as a
cross-compiler.

:     Todd> An in-tree toolchain build overrides this with just
:     Todd> /usr/lib, however.
:
: How to build this?

Not default yet.  This weekend it should all be made `live' for i386.

:     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...

Ah, you have LOCALBASE forced to /usr/local, eh?  Heh.  This is one of the
very conflicts that caused the pkgsrc architects to choose /usr/pkg as the
default....

-- 
-- Todd Vierling <tv@wasabisystems.com>  *  Wasabi NetBSD:  Run with it.
-- NetBSD 1.5 now available on CD-ROM  --  http://www.wasabisystems.com/