public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Wood <phillip.wood123@gmail.com>
To: Patrick Steinhardt <ps@pks.im>, Ben Knoble <ben.knoble@gmail.com>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
	"D. Ben Knoble" <ben.knoble+github@gmail.com>,
	git@vger.kernel.org, "Phillip Wood" <phillip.wood@dunelm.org.uk>,
	"Marc Branchaud" <marcnarc@xiplink.com>,
	"Evan Martin" <evan.martin@gmail.com>,
	"brian m. carlson" <sandals@crustytoothpaste.net>,
	"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH v6] build: regenerate config-list.h when Documentation changes
Date: Tue, 24 Feb 2026 11:00:54 +0000	[thread overview]
Message-ID: <39acbf7e-86f4-4dbe-8b58-3c04fccd7984@gmail.com> (raw)
In-Reply-To: <aZ12Lk85bSajirCY@pks.im>



On 24/02/2026 09:58, Patrick Steinhardt wrote:
> On Mon, Feb 23, 2026 at 04:41:48PM -0500, Ben Knoble wrote:
>>> Le 23 févr. 2026 à 01:55, SZEDER Gábor <szeder.dev@gmail.com> a écrit :
>>> On Sat, Feb 21, 2026 at 09:07:17AM -0500, D. Ben Knoble wrote:
>>>> diff --git a/Makefile b/Makefile
>>>> index 7f37ad8f58..6f926ffb1f 100644
>>>> --- a/Makefile
>>>> +++ b/Makefile
>>>> @@ -2688,9 +2688,10 @@ $(BUILT_INS): git$X
>>>>     cp $< $@
>>>>
>>>> config-list.h: generate-configlist.sh
>>>> +    @mkdir -p .depend
>>>> +    $(QUIET_GEN)$(SHELL_PATH) ./generate-configlist.sh . $@ .depend/config-list.h.d
>>>>
>>>> -config-list.h: Documentation/*config.adoc Documentation/config/*.adoc
>>>> -    $(QUIET_GEN)$(SHELL_PATH) ./generate-configlist.sh . $@
>>>> +-include .depend/config-list.h.d
>>>
>>> This breaks the build when something disappears from
>>> Documentation/config/:
>>>
>>>   $ git checkout origin/seen
>>>   HEAD is now at 57edfa3ce8 Merge branch 'ty/setup-error-tightening' into seen
>>>   $ ls -l Documentation/config/hook.adoc
>>>   -rw-rw-r-- 1 szeder szeder 3828 Feb 23 07:50 Documentation/config/hook.adoc
>>>   $ git grep hook.adoc
>>>   Documentation/git-hook.adoc:include::config/hook.adoc[]
>>>   Documentation/howto/meson.build:  'rebuild-from-update-hook.adoc',
>>>   Documentation/meson.build:  'git-hook.adoc' : 1,
>>>   $ make V=1 config-list.h
>>>   /bin/sh ./generate-configlist.sh . config-list.h .depend/config-list.h.d
>>>   $ git checkout 0aabf70f60
>>>   Previous HEAD position was 57edfa3ce8 Merge branch 'ty/setup-error-tightening' into seen
>>>   HEAD is now at 0aabf70f60 build: regenerate config-list.h when Documentation changes
>>>   $ ls -l Documentation/config/hook.adoc
>>>   ls: cannot access 'Documentation/config/hook.adoc': No such file or directory
>>>   $ git grep hook.adoc
>>>   Documentation/howto/meson.build:  'rebuild-from-update-hook.adoc',
>>>   Documentation/meson.build:  'git-hook.adoc' : 1,
>>>   $ make V=1 config-list.h
>>>   GIT_VERSION=2.53.0.119.g0aabf70f60
>>>   make: *** No rule to make target 'Documentation/config/hook.adoc', needed by 'config-list.h'.  Stop.
>>>   $ grep hook.adoc .depend/config-list.h.d
>>>   config-list.h: ./Documentation/config/hook.adoc
>>
>> Indeed. This might arise while bisecting, which was my original
>> motivation. Thoughts on a path forward? At least this issue (to me) is
>> clearer than a spurious test failure :)
> 
> For Meson this case works alright. So maybe we just drop the changes to
> the Makefile and call it a day?
> 
> An alternative would be to have the following patch on top:
> 
> diff --git a/generate-configlist.sh b/generate-configlist.sh
> index 39ac8845ab..e28054f9e0 100755
> --- a/generate-configlist.sh
> +++ b/generate-configlist.sh
> @@ -41,7 +41,12 @@ EOF
>   if test -n "$DEPFILE"
>   then
>   	QUOTED_OUTPUT="$(printf '%s\n' "$OUTPUT" | sed 's,[&/\],\\&,g')"
> -	printf '%s\n' "$SOURCE_DIR"/Documentation/*config.adoc \
> -		"$SOURCE_DIR"/Documentation/config/*.adoc |
> -		sed -e 's/[# ]/\\&/g' -e "s/^/$QUOTED_OUTPUT: /" >"$DEPFILE"
> +	{
> +		printf '%s\n' "$SOURCE_DIR"/Documentation/*config.adoc \
> +			"$SOURCE_DIR"/Documentation/config/*.adoc |
> +			sed -e 's/[# ]/\\&/g' -e "s/^/$QUOTED_OUTPUT: /"
> +		printf '%s:\n' "$SOURCE_DIR"/Documentation/*config.adoc \
> +			"$SOURCE_DIR"/Documentation/config/*.adoc |
> +			sed -e 's/[# ]/\\&/g'
> +	} >"$DEPFILE"
>   fi
> 
> What it does is to also create an empty target for all of the
> dependencies. Which is in fact what GCC/Clang also do when you pass -MP:

Oh, I was wondering how they got around the problem we're seeing here. 
While it seems ninja is happy it ignore missing dependencies in 
depfiles, are we sure the build systems meson uses on other platforms 
are as well? If not it might be worth adding this, rather than just 
dropping the Makefile changes.

Thanks

Phillip

> 
>      $ cat main.c
>      #include "foo.h"
>      int main()
>      {
>          puts("foobar");
>          return 0;
>      }
> 
>      $ clang -MMD -MP main.c
>      $ cat main.d
>      main.o: main.c foo.h
>      foo.h:
> 
> Patrick


  reply	other threads:[~2026-02-24 11:01 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-07 21:59 [PATCH] meson: regenerate config-list.h when Documentation changes D. Ben Knoble
2026-02-07 22:38 ` Ben Knoble
2026-02-09 15:19 ` [PATCH v2] " D. Ben Knoble
2026-02-11 23:51   ` [PATCH v3] " D. Ben Knoble
2026-02-12  8:06     ` Patrick Steinhardt
2026-02-12 10:29     ` Phillip Wood
2026-02-12 14:14       ` Phillip Wood
2026-02-12 15:56     ` Ben Knoble
2026-02-16 22:28     ` [PATCH v4] " D. Ben Knoble
2026-02-17  0:33       ` Ben Knoble
2026-02-17  7:03         ` Patrick Steinhardt
2026-02-17 13:28           ` D. Ben Knoble
2026-02-17  7:02       ` Patrick Steinhardt
2026-02-17 13:28         ` D. Ben Knoble
2026-02-17 20:24           ` Junio C Hamano
2026-02-17  9:20       ` Phillip Wood
2026-02-17 13:38         ` D. Ben Knoble
2026-02-17 15:11           ` Phillip Wood
2026-02-18 14:37       ` [PATCH v5] build: " D. Ben Knoble
2026-02-19 10:19         ` Phillip Wood
2026-02-19 13:40           ` D. Ben Knoble
2026-02-19 13:56         ` Patrick Steinhardt
2026-02-21 13:58           ` D. Ben Knoble
2026-02-19 15:10         ` Marc Branchaud
2026-02-21 13:58           ` D. Ben Knoble
2026-02-21 14:07         ` [PATCH v6] " D. Ben Knoble
2026-02-23  6:37           ` Patrick Steinhardt
2026-02-23  6:55           ` SZEDER Gábor
2026-02-23 21:41             ` Ben Knoble
2026-02-24  9:58               ` Patrick Steinhardt
2026-02-24 11:00                 ` Phillip Wood [this message]
2026-02-24 14:12                   ` D. Ben Knoble
2026-02-24 14:39           ` [PATCH v7] " D. Ben Knoble
2026-02-25 18:45             ` Junio C Hamano
2026-02-26  3:20               ` Ben Knoble
2026-02-09 15:25 ` [PATCH] meson: " Patrick Steinhardt
2026-02-09 21:50   ` D. Ben Knoble
2026-02-11  7:42     ` Patrick Steinhardt
2026-02-11  9:44       ` Phillip Wood
2026-02-11 10:57         ` Phillip Wood
2026-02-11 11:00           ` Patrick Steinhardt
2026-02-11 10:58         ` Patrick Steinhardt
2026-02-11 14:05           ` Phillip Wood
2026-02-11 20:15             ` D. Ben Knoble
2026-02-11 19:58       ` D. Ben Knoble
2026-02-12  8:10         ` Patrick Steinhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39acbf7e-86f4-4dbe-8b58-3c04fccd7984@gmail.com \
    --to=phillip.wood123@gmail.com \
    --cc=ben.knoble+github@gmail.com \
    --cc=ben.knoble@gmail.com \
    --cc=evan.martin@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=marcnarc@xiplink.com \
    --cc=phillip.wood@dunelm.org.uk \
    --cc=ps@pks.im \
    --cc=sandals@crustytoothpaste.net \
    --cc=szeder.dev@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox