Re: Makefile PATH modification with -current 'make'?

2017-02-15 Thread Simon Gerraty
Sorry, forgot to cc myself on last mail. What the failing makefile should probably be doing is using PREPEND_PATH += ${QTDIR}/bin rather than PATH:= ${QTDIR}/bin:${PATH} since _PATH_CMD has already been engaged - which is why PATH:= ${QTDIR}/bin:${PATH} is causing trouble. --sjg

Re: Makefile PATH modification with -current 'make'?

2017-02-15 Thread Simon Gerraty
>The problem with -current 'make' only showed up when I tried to build >"/usr/pkgsrc/wip/moto4lin". Prior to that, I built all packages in my >usual complement without incident (modulo pkg/51266). So the problem is _PATH_CMD in bsd.pkg.mk which is apparently used rarely - according to the

Re: Makefile PATH modification with -current 'make'?

2017-02-15 Thread John D. Baker
The most convenient additional system to test was -current/sparc. On: $ uname -a NetBSD lance.technoskunk.fur 7.99.59 NetBSD 7.99.59 (JEAN) #13: Mon Feb 13 17:15:42 CST 2017 sy...@x3650.technoskunk.fur:/r1/build/current/obj/sparc/sys/arch/sparc/compile/JEAN sparc running 'make clean' works,

Re: Makefile PATH modification with -current 'make'?

2017-02-15 Thread Simon Gerraty
>The problem with -current 'make' only showed up when I tried to build >"/usr/pkgsrc/wip/moto4lin". Prior to that, I built all packages in my >usual complement without incident (modulo pkg/51266). Ok might be something interesting about that package. Let me wade though the output you sent...

Re: Makefile PATH modification with -current 'make'?

2017-02-15 Thread John D. Baker
On Wed, 15 Feb 2017, John D. Baker wrote: > On Tue, 14 Feb 2017, Simon Gerraty wrote: > > > which AFAICT behaves as expected (current make on 7/amd64 and 7/i386) > > I've not tried running 'make' from -current on NetBSD-7. I just copied "/usr/bin/make" from a -current/amd64 system to a

Re: Makefile PATH modification with -current 'make'?

2017-02-15 Thread Joerg Sonnenberger
On Tue, Feb 14, 2017 at 06:05:55PM -0600, John D. Baker wrote: > Or is the package Makefile bogus and using an outdated mechanism? It is certainly bogus and should be using PREPEND_PATH. Whether it should work or not is a separate question. Joerg

Re: Makefile PATH modification with -current 'make'?

2017-02-15 Thread John D. Baker
On Tue, 14 Feb 2017, Simon Gerraty wrote: > >The curious item is that the very last line of "wip/moto4lin/Makefile" > > Sorry not familar with that - what's url to check it out? I'm not sure I understand. If you have a clone of the current pkgsrc-wip repository (typically under

Re: Makefile PATH modification with -current 'make'?

2017-02-15 Thread Simon Gerraty
Hi just a note to say, looking into your issue. Trying to reproduce (in a simpler example) ... no joy yet. Could you send me the output of 'ident /usr/bin/make' ? Thanks --sjg

Re: Makefile PATH modification with -current 'make'?

2017-02-15 Thread Simon Gerraty
>The curious item is that the very last line of "wip/moto4lin/Makefile" >is: Sorry not familar with that - what's url to check it out? >PATH:= ${QTDIR}/bin:${PATH} > >This produces the following on NetBSD/i386-7.99.59: > >$ make show-var VARNAME=PATH >/qt3/bin:16304path The

Makefile PATH modification with -current 'make'?

2017-02-14 Thread John D. Baker
Posting to current-users@ since it involves -current and to tech-pkg@ since it involves a pkgsrc-wip package. I've encountered a curious problem that shows up on NetBSD-current (amd64 and i386 so far), but not on netbsd-7. Attempting to build "wip/moto4lin" on NetBSD-current (7.99.59 amd64 and