Re: [bug #64288] The flag --no-print-directory becomes effective too early

(MAKE) --no-print-directory -f sub1/Makefile .PHONY: sub2 sub2: $(MAKE) --no-print-directory -f sub2/Makefile .PHONY: sub3 sub3: $(MAKE) --no-print-directory -f sub3/Makefile Previously, I was able to do "MAKEFLAGS += --no-print-directory" in a single place, but it is now impossible. -- Best Regards Masahiro Yamada

[bug #64288] The flag --no-print-directory becomes effective too early

Status: None ___ Follow-up Comments: --- Date: Fri 09 Jun 2023 08:15:30 AM UTC By: Masahiro Yamada Since 8f9e7722ff0f80d9f6ae9aba350ae02c3c6db878, --no-print-directory flag gets effecti

[bug #63417] .NOTINTERMEDIATE with no prerequisites is not working

Follow-up Comment #2, bug #63417 (project make): Thanks, the patch worked for me. ___ Reply to this item at: ___ Message sent via Savannah

[bug #63429] Escape sequence in logs are lost with -O option

: None ___ Follow-up Comments: --- Date: Sun 27 Nov 2022 02:32:02 AM UTC By: Masahiro Yamada While the -O option buffering the logs, the escape sequences for colors are lost. [Sample Ma

[bug #55532] Missing prerequisites are not included in $? if .SECONDARY is present

Follow-up Comment #6, bug #55532 (project make): Thanks, I agree with you. BTW, my main motivation was to suppress the auto-removal of intermediate files in the chained implicit rules. Make 4.4 introduced .NOTINTERMEDIATE. This is a better fit to my purpose because it has no side-effect to $?.

[bug #63417] .NOTINTERMEDIATE with no prerequisites is not working

: None ___ Follow-up Comments: --- Date: Fri 25 Nov 2022 09:16:11 PM UTC By: Masahiro Yamada The manual says: ".NOTINTERMEDIATE with no prerequisites causes all targets to

Re: False positive "doesn't match the target pattern" error

and make ./foo.x both produce the same file. > > regards, Dmitry This happens only for leading './'. 'foo' and '././././foo' are the same. Make considers 'foo/bar' and 'foo/./bar' as different targets. -- Best Regards Masahiro Yamada

Re: False positive "doesn't match the target pattern" error

On Sun, Aug 21, 2022 at 12:32 AM Dmitry Goncharov wrote: > > On Sat, Aug 20, 2022 at 5:52 AM Masahiro Yamada wrote: > > I appreciate GNU Make normalize the path > > by removing "./" > > > > This is helpful in some cases, but I think it is a bad side-effect

False positive "doesn't match the target pattern" error

for it. Or, any workaround exists? -- Best Regards Masahiro Yamada

[bug #61218] The -e option confuses the $(origin )

URL: Summary: The -e option confuses the $(origin ) Project: make Submitted by: masahiroy Submitted on: Sat 25 Sep 2021 07:12:00 AM UTC Severity: 3 - Normal Item Group:

[bug #58529] MAKEOVERRIDES does not change the origin

Follow-up Comment #4, bug #58529 (project make): > "$(MAKE)" appears in a recipe it will be replaced with the equivalent of "make > $(MAKEOVERRIDES)" or in this case, "make FOO=y". Make sense. I agree this is not a bug. Thanks for explanation.

[bug #58529] MAKEOVERRIDES does not change the origin

Follow-up Comment #1, bug #58529 (project make): MAKEOVERRIDES += FOO=overridden-value in the test code is: MAKEOVERRIDES += FOO=y ___ Reply to this item at:

[bug #58529] MAKEOVERRIDES does not change the origin

URL: Summary: MAKEOVERRIDES does not change the origin Project: make Submitted by: masahiroy Submitted on: Mon 08 Jun 2020 04:56:27 AM UTC Severity: 3 - Normal Item

Re: [bug #56834] PATH not honored when --disable-posix-spawn is not used

make/src/job.c:141:11: fatal error: findprog.h: No such file or directory # include "findprog.h" ^~~~ compilation terminated. make[1]: *** [Makefile;1197: src/job.o] Error 1 make[1]: *** Waiting for unfinished jobs make[1]: Leaving directory '/tmp/build-make' make: ***

[bug #56778] 'define' ... 'endef' serializes sub-make invocations

URL: Summary: 'define' ... 'endef' serializes sub-make invocations Project: make Submitted by: masahiroy Submitted on: Tue 20 Aug 2019 04:31:17 AM UTC Severity: 3 - Normal

Re: Idea: Allow $(name ...) as an abbrevation of $(call name ....)

...) . Linux kernel build system highly exploits recursive building. So, I avoid using $(shell ...) in the recursively-invoked Makefiles. -- Best Regards Masahiro Yamada ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make

Re: Idea: Allow $(name ...) as an abbrevation of $(call name ....)

,$$(error too few arguments))$$(if $$($(2)),$$(error too many arguments)) my-dummy = $(eval $(call arg-check,1,3))echo $(1) $(2) ---(sample code 2 end)------ -- Best Regards Masahiro Yamada ___ Bug-make mailing list Bug-make@gn

Re: Idea: Allow $(name ...) as an abbrevation of $(call name ....)

On Mon, Jun 10, 2019 at 12:46 PM David A. Wheeler wrote: > > On Mon, 10 Jun 2019 11:56:04 +0900, Masahiro Yamada > wrote: > > It is a design. > > Sure, but we can add to it. > > > In summary, there is slight difference between > > a variable and a user-

Re: Idea: Allow $(name ...) as an abbrevation of $(call name ....)

Hi. On Mon, Jun 10, 2019 at 10:55 AM Paul Smith wrote: > > On Sun, 2019-06-09 at 18:53 -0400, David A. Wheeler wrote: > > There's also no need for it. If "name" is followed by whitespace it *cannot* > > be a POSIX variable reference, because POSIX doesn't allow that. > > > > Solution: > > Just

Re: Idea: Allow certain special targets as dependencies

et forcibly, but I think it is slightly different from .PHONY. -- Best Regards Masahiro Yamada ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make

[bug #55532] Missing prerequisites are not included in $? if .SECONDARY is present

Follow-up Comment #4, bug #55532 (project make): > It's extremely difficult to understand your bug report > because you keep talking about $^ but after a lot of > confused reading of your report and a close look at your > example it's obvious you really mean $? everywhere you write $^. Sorry

[bug #56301] Mandatory/Optional include files and pattern rule with multi-targets

URL: Summary: Mandatory/Optional include files and pattern rule with multi-targets Project: make Submitted by: masahiroy Submitted on: Fri 10 May 2019 04:33:49 PM UTC Severity: 3 -

[bug #51495] Notice when a rule changed, so target needs rebuilding

Follow-up Comment #4, bug #51495 (project make): I have not read "GNU Make Book". Anyway, IIRC, the document of ninja-build mentioned it had borrowed the idea from Linux Kernel build system. Linux kernel build system works with GNU Make, and achieved the similar feature by meta-programming.

Re: [Question] multiple targets for implicit rule

On Wed, Feb 20, 2019 at 1:04 AM LeJacq, Jean Pierre wrote: > > On Tuesday, February 19, 2019 10:51:42 AM EST Masahiro Yamada wrote: > > > > (Makefile begin)- > > .PHONY: all > > all: foo.x foo.z > > > > %.x %.z: > >

[Question] multiple targets for implicit rule

targets appear in one implicit rule, Make runs the recipe just once instead of twice even when it is requested to create two targets. In this case, does Make assume the recipe will create both %.x and %.z ? Is this behavior intentional? Documented somewhere? -- Best Regards Masahiro Yamada

[bug #55720] Make cannot execute shell-builtin commands in recipe

Follow-up Comment #1, bug #55720 (project make): I take back this report. I was using a released version. The git version is fine. This issue was fixed by the following commit. commit 1af314465e5dfe3e8baa839a32a72e83c04f26ef * job.c: Add "command" as a known shell built-in. Sorry for

[bug #55720] Make cannot execute shell-builtin commands in recipe

URL: Summary: Make cannot execute shell-builtin commands in recipe Project: make Submitted by: masahiroy Submitted on: Sat 16 Feb 2019 10:11:05 AM UTC Severity: 3 - Normal

[bug #55719] Variables containing hyphens are not exported

URL: Summary: Variables containing hyphens are not exported Project: make Submitted by: masahiroy Submitted on: Sat 16 Feb 2019 09:29:01 AM UTC Severity: 3 - Normal

Re: Why is $? affected by .SECONDARY ?

Hi Paul, On Mon, Jan 21, 2019 at 7:45 AM Paul Smith wrote: > > On Sun, 2019-01-13 at 11:19 +0900, Masahiro Yamada wrote: > > [Test Code 2] > > -->8--- > > foo: bar FORCE > > @echo newer prerequisites are: $? > >

Why is $? affected by .SECONDARY ?

Oh. $? does not include 'bar' and 'FORCE' any more despite they do not exist. Why is $? affected by the .SECONDARY special target? Is this intentional? -- Best Regards Masahiro Yamada ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu

Re: Why is --include-dir option effective only in sub make ?

Hi Paul, 2018-09-13 21:34 GMT+09:00 Paul Smith : > On Thu, 2018-09-13 at 14:18 +0900, Masahiro Yamada wrote: >> I wonder why --include-dir does not become >> effective in the current Makefile. > > In order for this to work, the MAKEFLAGS variable would have to be re

Why is --include-dir option effective only in sub make ?

ter diving into sub make. Is this an intentional behavior? Is there a way to make it effective in the current make? -- Best Regards Masahiro Yamada ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make

Re: Parallel building of Linux Kernel is broken

; -Mike Yes, with this change, I can build Linux kernel in parallel now. Thank you! -- Best Regards Masahiro Yamada ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make

Re: Parallel building of Linux Kernel is broken

: touch auto.conf --(Makefile.config END)--- [How to run the test case?] $ make -j8 config all Thanks. 2018-08-09 11:47 GMT+09:00 Masahiro Yamada : > Hello. > > > > 2018-07-12 20:55 GMT+09:00 Masahiro Yamada : >> 2018-07-12

Re: Parallel building of Linux Kernel is broken

Hello. 2018-07-12 20:55 GMT+09:00 Masahiro Yamada : > 2018-07-12 20:26 GMT+09:00 Paul Smith : >> On Thu, 2018-07-12 at 14:51 +0900, Masahiro Yamada wrote: >>> I attached information that might be helpful. >>> Please take it FWIW. >> >> The content you

Re: Parallel building of Linux Kernel is broken

2018-07-12 20:26 GMT+09:00 Paul Smith : > On Thu, 2018-07-12 at 14:51 +0900, Masahiro Yamada wrote: >> I attached information that might be helpful. >> Please take it FWIW. > > The content you quote looks correct to me so if that's what's really in > the makefiles then

Re: Parallel building of Linux Kernel is broken

Hi. 2018-07-12 14:13 GMT+09:00 Paul Smith : > On Thu, 2018-07-12 at 13:55 +0900, Masahiro Yamada wrote: >> Please add V=1 to the build command, like this: >> >> $ make -j8 V=1 defconfig all >> >> It will emit _almost_ raw log. > > At this time I don't have

Re: Parallel building of Linux Kernel is broken

Hi. 2018-07-12 13:37 GMT+09:00 Paul Smith : > On Thu, 2018-07-12 at 10:26 +0900, Masahiro Yamada wrote: >> $ make -j8 defconfig all >> HOSTCC scripts/basic/fixdep >> HOSTCC scripts/kconfig/conf.o >> YACCscripts/kconfig/zconf.tab.c >> LEX script

Parallel building of Linux Kernel is broken

Kconfig make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. SYSTBL arch/x86/include/generated/asm/syscalls_32.h The commit subject says 'Clean up', but I think this is accidental breakage. Any clue? -- Best Regards Masahiro Yamada