On Sun, 2 Nov 2003, Johnny C. Lam wrote:

> If you're running with LOCALBASE=/usr, I think you're probably going
> to run into this situation many more times.  Buildlink won't stop

But it has been very rare. I have been using LOCALBASE=/usr on probably
over 15 installs or systems to build over 250 packages over the past 14
months. (Packages that I consider essential to a running system and then
other interesting and popular software like KDE, Mozilla, The GIMP and
more.)

LOCALBASE=/usr has been working great for me. I am glad that pkgsrc has
been so portable and easy to make this work.

As for this aalib, since we don't include ncurses buildlink2.mk in the
first place then it will be safe (and no change) to make sure that it
configures with --with-curses-driver=no. I will do this on Monday unless
someone decides that ncurses is needed.

> GNU configure scripts from finding libraries and headers not in the
> .buildlink directory because they'll all be readily available in
> /usr/lib.  I don't really have a solution for this in mind yet.  I
> think it may be possible to create some sort of pkgtools/system-links
> package that has system libraries and headers (analogous to x11-links
> and X11R6 libs and headers) and force the compiler/linker to be passed
> "-nostdinc" and "-nostdlib".  This hypothethical system-links package
> would have to be unique for each OS.  If anyone else wants to pursue
> this idea and would like some guidance, please send me private email.

I will reply to that in private email ... since I was already thinking
about making buildlink2.mk files for my glibc and linux-kernel-headers
packages (which are the only packages I have in an entire Linux install
that are not using buildlink2.mk ... if you count x11-links to cover
wip/XFree86-libs).

   Jeremy C. Reed
   http://bsd.reedmedia.net/

p.s. If anyone wonders ... yes, I sit at NetBSD :)