Subject: buildlink3 and /usr/lib (was Re: CVS commit: pkgsrc)
To: None <>
From: Jeremy C. Reed <>
List: tech-pkg
Date: 08/06/2004 10:11:11
On Fri, 6 Aug 2004, Johnny C. Lam wrote:
> Log Message:
> Clear up a common misconception about buildlink3.  The reality is that
> everything in /usr/include and /usr/lib (system header and library
> paths) is always considered part of the package build environment;
> buildlink3 only isolates package builds from everything outside of
> those system paths.  As a consequence of this, LOCALBASE == "/usr"
> effectively makes buildlink3 do nothing.

Thank you for improving Packages.txt to further explain this.

My main problem occurs even when I use default LOCALBASE as /usr/pkg. This
is when I use one build system that detects alsalibs or some curses and
then I try to use the packages on another system that doesn't have the
alsalibs or has a different ABI for other libraries. alsa libraries (like
libasound) is an example of something that pkgsrc doesn't provide yet (it
is in pkgsrc-wip).

I don't know what can be done, but maybe it would be nice to also stop
/usr/lib and /usr/include too, so packages transfered to other systems
will probably work better.

 Jeremy C. Reed

 	  	 	 BSD News, BSD tutorials, BSD links