Subject: Re: new feature for bmake: read-only variables
To: None <tech-pkg@netbsd.org>
From: Jeroen Ruigrok/asmodai <asmodai@in-nomine.org>
List: tech-pkg
Date: 09/02/2005 15:03:31
-On [20050902 12:51], Jeroen Ruigrok/asmodai (asmodai@in-nomine.org) wrote:
>Well, someone must've fixed the bmake show-options in recent weeks. The
>portable one from sjg now works correctly and shows the ones that are
>enabled. Previously only bootstap's bmake worked as it should.
Hmm, found a small issue again:
(/usr/pkgsrc/meta-pkgs/xorg)
[14:03] [root@purgatory] (520) {0} # /usr/pkg/bin/bmake fetch
===> *** No /usr/pkgsrc/distfiles/pkg-vulnerabilities file found,
===> *** skipping vulnerability checks. To fix, install
===> *** the pkgsrc/security/audit-packages package and run
===> *** '/usr/pkg/sbin/download-vulnerability-list'.
(/usr/pkgsrc/meta-pkgs/xorg)
[14:03] [root@purgatory] (521) {0} # bmake-20050530 fetch
===> X11_TYPE=xorg is mandatory.
(/usr/pkgsrc/meta-pkgs/xorg)
[14:03] [root@purgatory] (522) {0} # bmake-20050606 fetch
===> X11_TYPE=xorg is mandatory.
Aha.
Found what the issue is. Relatively simple in a way. For projects I run
I've told people to use Simon's bmake releases. That's wonderful, have it
installed and been wondering what was causing problems with the pkgsrc
trees.
Compared the bmake -dA output:
--- /home/asmodai/bmake-boot.log 2005-09-02 14:11:46.000000000 +0200
+++ /home/asmodai/bmake-20050606.log 2005-09-02 14:05:16.000000000 +0200
[snip]
-Caching /usr/pkg/share/mk...done
-expanding "sys.mk".../usr/pkg/share/mk/sys.mk
-Global:MAKEFILE = /usr/pkg/share/mk/sys.mk
-Global:.PARSEDIR = /usr/pkg/share/mk
+Caching /usr/share/mk ...done
+Caching /share/mk ...done
+Caching /usr/local/share/mk ...done
+Caching /opt/share/mk ...done
+Expanding "sys.mk"... /usr/share/mk/sys.mk
+Global:MAKEFILE = /usr/share/mk/sys.mk
+Global:.PARSEDIR = /usr/share/mk
Which makes sense if you look at the devel/bmake port:
makesyspath=${PREFIX}/share/mk:/usr/share/mk:/usr/local/share/mk:/opt/share/mk
CONFIGURE_ARGS+= --with-default-sys-path=${makesyspath}
Which of course not what I initially compile bmake with. If I add that to
my own compiled bmakes then I don't have the issues anymore.
Just makes me wonder if this is necessary or if the top-level pkgsrc
Makefiles should perhaps use -m somewhere to override the default system
include path.
--
Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono
Free Tibet! http://www.savetibet.org/ | http://www.andf.info/
http://www.tendra.org/ | http://www.in-nomine.org/
A journey of a thousand miles starts with a single step. - Chinese Proverb