From: Christian Biesinger via Gdb-patches <gdb-patches@sourceware.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Matthias Klose <doko@ubuntu.com>,
GDB <gdb-patches@sourceware.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Binutils <binutils@sourceware.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: V3 [PATCH 5/5] gnulib: Support variables from the top level Makefile
Date: Tue, 5 Jan 2021 14:26:41 +0100 [thread overview]
Message-ID: <CAPTJ0XGAPAn=QQ-d8Vm1mp0_Szd8+xn0eob9Hni6_+Ysqifbqg@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOo9gcoyZWuiEQ5_FmSwBBxaPBt9Z0rV+1=hn4iM-cb83Q@mail.gmail.com>
On Fri, Jan 1, 2021 at 1:07 AM H.J. Lu via Gdb-patches
<gdb-patches@sourceware.org> wrote:
>
> On Thu, Dec 31, 2020 at 3:50 PM Joseph Myers <joseph@codesourcery.com> wrote:
> >
> > On Sat, 19 Dec 2020, H.J. Lu via Gcc-patches wrote:
> >
> > > Work around what appears to be a GNU make bug handling MAKEFLAGS
> > > values defined in terms of make variables, as is the case for CC and
> > > friends when we are called from the top level Makefile.
> >
> > This description, and the comment in Makefile.am repeating it, is rather
> > unhelpful as it provides no way for a reader to know what the supposed bug
> > is. Reviewers need to be able to work out whether the proposed workaround
> > is correct or the right approach for working around the bug. Maintainers
> > in future need to be able to tell what the bug is. So the comment needs
> > to explain what the bug is and give a reference to a report for the bug in
> > the GNU make bug tracker, so that subsequent maintainers can look at that
> > bug to tell if the workaround is still needed at all.
> >
>
> I just copied the same workaround from other directories in GCC.
But could you explain under which circumstances the bug happens?
Christian
next prev parent reply other threads:[~2021-01-05 13:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 18:10 V3 [PATCH 0/5] Support the PGO build for binutils+gdb H.J. Lu via Gdb-patches
2020-12-19 18:10 ` V3 [PATCH 1/5] GCC: Pass --plugin to AR and RANLIB H.J. Lu via Gdb-patches
2020-12-19 18:10 ` V3 [PATCH 2/5] Binutils: " H.J. Lu via Gdb-patches
2020-12-19 18:10 ` V3 [PATCH 3/5] Support the PGO build for binutils+gdb H.J. Lu via Gdb-patches
2021-02-28 7:01 ` Mike Frysinger via Gdb-patches
2021-02-28 12:44 ` [PATCH] Add missing changes to Makefile.tpl H.J. Lu via Gdb-patches
2020-12-19 18:10 ` V3 [PATCH 4/5] Set TESTS to gdb.dwarf2/*.exp for PGO build training H.J. Lu via Gdb-patches
2020-12-19 18:10 ` V3 [PATCH 5/5] gnulib: Support variables from the top level Makefile H.J. Lu via Gdb-patches
2020-12-31 23:50 ` Joseph Myers
2021-01-01 0:06 ` H.J. Lu via Gdb-patches
2021-01-05 13:26 ` Christian Biesinger via Gdb-patches [this message]
2021-01-05 14:06 ` H.J. Lu via Gdb-patches
2021-01-02 19:22 ` V3 [PATCH 0/5] Support the PGO build for binutils+gdb Segher Boessenkool
2021-01-02 19:46 ` H.J. Lu via Gdb-patches
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='CAPTJ0XGAPAn=QQ-d8Vm1mp0_Szd8+xn0eob9Hni6_+Ysqifbqg@mail.gmail.com' \
--to=gdb-patches@sourceware.org \
--cc=binutils@sourceware.org \
--cc=cbiesinger@google.com \
--cc=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=joseph@codesourcery.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