Re: svn commit: r250699 - in head: share/mk usr.bin/make

2013-05-18 Thread Simon J. Gerraty
On Fri, 17 May 2013 23:34:08 +0200, Tijl Coosemans writes: _PORTCONF!=3D/usr/local/libexec/portconf =2Efor i in ${_PORTCONF:S/|/ /g} ${i:S/%/ /g} Is it possible to re-write this to be less dependent on how .for is parsed? Eg. assuming i is foo=[%]blah%goo ${i:C,=.*,,g} = ${i:C,.*=%*,,:S,%, ,g}

Re: svn commit: r250699 - in head: share/mk usr.bin/make

2013-05-17 Thread Tijl Coosemans
On 2013-05-16 17:28, Simon J. Gerraty wrote: Author: sjg Date: Thu May 16 15:28:38 2013 New Revision: 250699 URL: http://svnweb.freebsd.org/changeset/base/250699 Log: Build bmake by default. For me /usr/src is a symlink to /some/path and now if I build from /usr/src some parts end up in

Re: svn commit: r250699 - in head: share/mk usr.bin/make

2013-05-17 Thread Simon J. Gerraty
For me /usr/src is a symlink to /some/path and now if I build from /usr/src some parts end up in /usr/obj/usr/src and other parts in /usr/obj/some/path. It used to be the latter. This could be the result of some bits being built by the old freebsd make. Since the early stage of buildworld

Re: svn commit: r250699 - in head: share/mk usr.bin/make

2013-05-17 Thread Tijl Coosemans
On 2013-05-17 21:39, Simon J. Gerraty wrote: For me /usr/src is a symlink to /some/path and now if I build from /usr/src some parts end up in /usr/obj/usr/src and other parts in /usr/obj/some/path. It used to be the latter. This could be the result of some bits being built by the old freebsd

Re: svn commit: r250699 - in head: share/mk usr.bin/make

2013-05-17 Thread Simon J. Gerraty
On Fri, 17 May 2013 23:34:08 +0200, Tijl Coosemans writes: When the output of /usr/local/libexec/portconf is empty make warns about it: Yes. This is to avoid accidents. If you *know* that no output is a valid result, you can add '; echo' to the end of the command to suppress the warning.

Re: svn commit: r250699 - in head: share/mk usr.bin/make

2013-05-17 Thread Jilles Tjoelker
On Fri, May 17, 2013 at 03:28:10PM -0700, Simon J. Gerraty wrote: On Fri, 17 May 2013 23:34:08 +0200, Tijl Coosemans writes: When the output of /usr/local/libexec/portconf is empty make warns about it: Yes. This is to avoid accidents. If you *know* that no output is a valid result, you can