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 22:08:26
>>>>> "Todd" == Todd Vierling <tv@wasabisystems.com> writes:
Todd> : Todd> An in-tree toolchain build overrides this with just
Todd> : Todd> /usr/lib, however.
Todd> :
Todd> : How to build this?
Todd> Not default yet. This weekend it should all be made `live'
Todd> for i386.
That means a simple 'USE_NEW_TOOLCHAIN=1' in /etc/mk.conf will replace
the older egcs and binutils stuff with the 'new' toolchain ones?
Todd> : Several pkgsrc stuff requires/builds the pkgsrc/devel/gettext-lib
Todd> : (libintl.so.1) which superseeds the system /usr/lib/libintl.so.0. Then
Todd> : this odyssey began...
Todd> Ah, you have LOCALBASE forced to /usr/local, eh? Heh. This is one of the
Todd> very conflicts that caused the pkgsrc architects to choose /usr/pkg as the
Todd> default....
Worse:
$ ls -l /usr/pkg
lrwxr-xr-x 1 root wheel 5 Jul 2 2000 /usr/pkg@ -> local
My first thought that time was their purpose would be quite the same.
... and I didn't like to add another search path for binaries... :-/
But why is pkgsrc/devel/gettext-lib needed by some other pkgsrc stuff
if /usr/lib/libintl.* is present?
Markus.