Subject: pkg/18940: some packages fail to build if /usr/pkg/bin is not in PATH
To: None <firstname.lastname@example.org>
From: None <email@example.com>
Date: 11/05/2002 13:09:55
>Synopsis: some packages fail to build if /usr/pkg/bin is not in PATH
>Arrival-Date: Tue Nov 05 04:11:00 PST 2002
>Originator: Urban Boquist
>Release: NetBSD 1.6K
Carlstedt Research & Technology AB, Sweden
System: NetBSD iller 1.6K NetBSD 1.6K (ILLER-$Revision: 1.51 $) #0: Sat Nov 2 15:39:05 CET 2002 root@iller:/usr/src/sys/arch/i386/compile/ILLER i386
I just built some packages in a chroot (using pkgsrc/mk/bulk/mksandbox)
and somehow ended up with a shell where /usr/pkg/bin was not in
PATH. The following packages failed to build:
archivers/zip (tries to run "unzip")
print/teTeX-bin (tries to run "texconfig")
devel/php4-gettext (mysterious error)
databases/php4-mysql (mysterious error)
adding /usr/pkg/bin to PATH and restarting the build solved all the problems.
Build packages using pkgsrc/mk/bulk/mksandbox.
Not sure, but it seems to me that if some package require /usr/pkg/bin
in PATH this should "just work", no matter what the shell that I start
the build from is set to. Especially since this was the default that I
got from "mksandbox".
It also seems that this somehow ought to be handled by bsd.pkg.mk, and
not in individual packages (the ones above are just those I happened
to stumble upon, I built far from the entire pkgsrc). I haven't looked
at the code at all though, maybe there already is some special PATH handling.