Subject: Re: Toolchain Update (27-Nov-2001)
To: None <email@example.com>
From: John Darrow <John.P.Darrow@wheaton.edu>
Date: 11/28/2001 12:43:12
gabriel rosenkoetter <firstname.lastname@example.org> wrote:
>[Adding tech-pkg in here, since it's not clear that this is entirely,
>or at all, a toolchain problem. As summary: I had a USETOOLS and DESTDIR
>set with in a #ifndef BSD_PKG_MK in my /etc/mk.conf. For a while,
>this meant that packages, correctly, used the installed tools to
>build, linked against things under / rather than under DESTDIR, but
>that broke about a week ago.]
>On Wed, Nov 28, 2001 at 12:26:44AM -0500, James Chacon wrote:
>> I'd have to look at the exact package but some of the sub makes do not read
>> in bsd.pkg.mk but do read in the system .mk files.
>Okay, so I hadn't even looked yet, but pkgsrc/graphics/apla very
>definitely DOES have a .include "../../mk/bsd.pkg.mk". It's the
>It also does not include any other bsd.*.mks. I can't see why this
>is cropping up, though, since bsd.pkg.mk includes bsd.prefs.mk
>before it does anything with USETOOLS, and bsd.prefs.mk sets
>BSD_PKG_MK (which strikes me as wrong, but whatever).
I had a sneaking suspicion what this was, and I just untarred an
apla distfile and confirmed it.
The problem is not in the pkgsrc Makefiles themselves, but further in,
in the third party Makefiles which themselves use BSD make .include
files as part of their build process.
These Makefiles have no clue that they're running as part of a pkgsrc
build, and as such, if pkgsrc is located inside /usr/src, end up
catching all the tools framework.
I don't have a -current setup to test on, but would a simple
MAKE_ENV+="BSD_PKG_MK=" (or something like that) in bsd.pkg.mk, thus
causing the inner makes' include of mk.conf to also see that it's
inside a pkgsrc build, fix this problem?
John Darrow - Senior Technical Specialist Office: 630/752-5201
Computing Services, Wheaton College, Wheaton, IL 60187 Fax: 630/752-5968
Pager via email: email@example.com Pager: 630/316-0707
Email: John.P.Darrow@wheaton.edu (plain text please, no HTML or proprietary)