Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>,
	Simon Marchi <simon.marchi@efficios.com>,
	Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/7] gdb, gdbserver: require gcc-style dependency generation, drop the depcomp fallback
Date: Tue, 1 Sep 2026 16:16:42 -0400	[thread overview]
Message-ID: <6ae22222-818f-46f8-97c1-0237d7fa1839@simark.ca> (raw)
In-Reply-To: <878q5l7x0p.fsf@tromey.com>



On 2026-09-01 12:32, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
> 
> Simon> gdb/Makefile.in and gdbserver/Makefile.in have similar code to do manual
> Simon> gcc3-style dependency tracking, or fallback to the depcomp tool for
> Simon> other dependency tracking modes.  I believe that in this day and age, we
> Simon> can assume that all compilers we support know about gcc3-style
> Simon> dependency tracking.
> 
> Simon> Obviously, gcc and clang both know about it.  The other compilers I am
> Simon> aware of (I don't even know if they can build GDB) are Intel icc and IBM
> Simon> XL, and they both appear to have known about it for a while.
> 
> I wonder if the Windows or Solaris compilers work.

If by Windows you mean MSVC, I would be really surprised.

I did not know about the Sun Studio compiler, but I would assume that
people juste use gcc to build gdb on Solaris.  Rainer, is that true?

> Anyway, I'm fine with this.  I tend to doubt anybody uses anything else,
> on the theory that if they did, we'd probably have seen patches to work
> around problems.  I suppose we can revert this or just ask people to
> write wrapper scripts for any compiler not supporting this feature.
> 
> The depcomp stuff was more important for C and the olden times when
> other compilers were in use.
> 
> Approved-By: Tom Tromey <tom@tromey.com>

Thanks,

Simon

  reply	other threads:[~2026-09-01 20:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31 18:51 [PATCH 0/7] Some Makefile cleanups Simon Marchi
2026-08-31 18:51 ` [PATCH 1/7] gdb: update README about the GNU make requirement Simon Marchi
2026-09-01 12:26   ` Eli Zaretskii
2026-09-01 13:36     ` Simon Marchi
2026-08-31 18:51 ` [PATCH 2/7] gdb, gdbserver: require gcc-style dependency generation, drop the depcomp fallback Simon Marchi
2026-09-01 16:32   ` Tom Tromey
2026-09-01 20:16     ` Simon Marchi [this message]
2026-09-02  7:37       ` Rainer Orth
2026-09-02 12:26         ` Simon Marchi
2026-08-31 18:51 ` [PATCH 3/7] gdbserver: fix missing dependency tracking for gdbreplay.o Simon Marchi
2026-09-01 16:33   ` Tom Tromey
2026-08-31 18:51 ` [PATCH 4/7] gdb, gdbserver: always use order-only prerequisites for generated files Simon Marchi
2026-09-01 16:34   ` Tom Tromey
2026-08-31 18:51 ` [PATCH 5/7] gdb, gdbserver: remove the .NOEXPORT target Simon Marchi
2026-09-01 16:37   ` Tom Tromey
2026-08-31 18:51 ` [PATCH 6/7] gdb: remove the explicit ada-exp.o rule Simon Marchi
2026-09-01 16:38   ` Tom Tromey
2026-08-31 18:51 ` [PATCH 7/7] gdb, gdbserver: create the dependency directories from the Makefiles Simon Marchi
2026-09-01 16:47   ` Tom Tromey
2026-09-01 20:18     ` Simon Marchi
2026-09-01 20:37       ` Simon Marchi
2026-09-02 18:36         ` Tom Tromey
2026-09-03 13:45           ` Simon Marchi

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=6ae22222-818f-46f8-97c1-0237d7fa1839@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    --cc=simon.marchi@efficios.com \
    --cc=tom@tromey.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