On Fri, 17 May 2024, Edgar Fuß wrote:
What happens here is that the child "make -V" reads the complete Makefile
again, and after that, it prints the variable value.
Oh, then it's propably useless in the pkgsrc context the question came up.
There's a trick to do this, but for it to work, comp
> What happens here is that the child "make -V" reads the complete Makefile
> again, and after that, it prints the variable value.
Oh, then it's propably useless in the pkgsrc context the question came up.
17.05.2024 15:50:06 Edgar Fuß :
>> main: .PHONY
>> make -V X | wc -c
> Wow, I didn't know that worked.
>
> How on earth /does/ it work? If a command happens to be "make", make just
> forks without the child process exec()ing anything, so all the make variables
> etc. are inherited?
No, that w
> main: .PHONY
> make -V X | wc -c
Wow, I didn't know that worked.
How on earth /does/ it work? If a command happens to be "make", make just
forks without the child process exec()ing anything, so all the make variables
etc. are inherited?
nia writes:
> greetz,
>
> Here's the latest version with all required changes
This is on a -current vm...
$ uname -a
NetBSD beasty.blahblah.com 10.99.10 NetBSD 10.99.10 (GENERIC64) #0: Fri May 3
09:00:59 UTC 2024
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/evbarm/compile/GENERIC64 evbarm
I
greetz,
Here's the latest version with all required changes
nbupgrade.tar.gz
Description: Binary data
