Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb] Remove gdb-gdb.gdb dependency in make all rule
Date: Fri, 04 Sep 2026 14:12:37 +0100	[thread overview]
Message-ID: <878q5hrwhm.fsf@redhat.com> (raw)
In-Reply-To: <20260904104428.478890-1-tdevries@suse.de>

Tom de Vries <tdevries@suse.de> writes:

> In gdb/Makefile.in we have:
> ...
> all: gdb$(EXEEXT) $(CONFIG_ALL) gdb-gdb.gdb gcore gstack gdb-add-index
> ...
>
> The dependency on gdb-gdb.gdb made sense before commit ffeb311d2cd
> ("[gdb/build] Rename gdb/gdb-gdb.gdb.in to gdb/gdb-gdb.gdb"), but now we
> use AC_CONFIG_LINKS and there's no longer a corresponding make rule.
>
> Remove gdb-gdb.gdb from the dependency list.

Makes sense.

Approved-By: Andrew Burgess <aburgess@redhat.com>

Thanks,
Andrew


> ---
>  gdb/Makefile.in | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gdb/Makefile.in b/gdb/Makefile.in
> index 767f9280864..d8db6eecf0f 100644
> --- a/gdb/Makefile.in
> +++ b/gdb/Makefile.in
> @@ -2088,7 +2088,7 @@ generated_files = \
>  # Flags needed to compile Python code
>  PYTHON_CFLAGS = @PYTHON_CFLAGS@
>  
> -all: gdb$(EXEEXT) $(CONFIG_ALL) gdb-gdb.gdb gcore gstack gdb-add-index
> +all: gdb$(EXEEXT) $(CONFIG_ALL) gcore gstack gdb-add-index
>  	@$(MAKE) $(FLAGS_TO_PASS) DO=all "DODIRS=$(SUBDIRS)" subdir_do
>  
>  # Rule for compiling .c files.
>
> base-commit: 32090b27e92cb8fd4998e8e8e65d43f445545bc7
> -- 
> 2.51.0


      reply	other threads:[~2026-09-04 13:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 10:44 Tom de Vries
2026-09-04 13:12 ` Andrew Burgess [this message]

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=878q5hrwhm.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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