From: David Malcolm <dmalcolm@redhat.com>
To: Romain Naour <romain.naour@gmail.com>, gcc-patches@gcc.gnu.org
Cc: Ben Dakin-Norris <ben.dakin-norris@navtechradar.com>,
Maxim Kochetkov <fido_max@inbox.ru>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
"Cc : David Malcolm" <dmalcolm@gcc.gnu.org>
Subject: Re: [PATCH] gcc/Makefile.in: move SELFTEST_DEPS before including language makefile fragments
Date: Thu, 21 May 2020 18:13:15 -0400 [thread overview]
Message-ID: <841760282407434eaf7ebca396108953d0be655e.camel@redhat.com> (raw)
In-Reply-To: <20200521153519.2858998-1-romain.naour@gmail.com>
On Thu, 2020-05-21 at 17:35 +0200, Romain Naour wrote:
> As reported by several Buildroot users [1][2][3], the gcc build
> may fail while running selftests makefile target.
>
> The problem only occurs when ccache is used with gcc 9 and 10,
> probably due to a race condition.
>
> While debuging with "make -p" we can notice that s-selftest-c target
> contain only "cc1" as dependency instead of cc1 and SELFTEST_DEPS
> [4].
>
> s-selftest-c: cc1
>
> While the build is failing, the s-selftest-c dependencies recipe is
> still running and reported as a bug by make.
>
> "Dependencies recipe running (THIS IS A BUG)."
>
> A change [5] in gcc 9 seems to introduce the problem since we can't
> reproduce this problem with gcc 8.
Sorry about introducing the breakage. The patch looks sane to me,
though I don't know if I can formally approve it (and I'm now doubting
my "make" skills...)
Dave
next prev parent reply other threads:[~2020-05-21 22:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 15:35 Romain Naour
2020-05-21 17:31 ` Richard Biener
2020-05-21 17:41 ` Jeff Law
2020-05-30 11:32 ` Romain Naour
2020-05-21 22:13 ` David Malcolm [this message]
2020-05-27 12:04 ` Romain Naour
2020-06-03 18:33 ` Jeff Law
2020-06-03 19:56 ` Romain Naour
2020-06-03 20:24 ` Jeff Law
2020-07-08 19:41 ` Romain Naour
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=841760282407434eaf7ebca396108953d0be655e.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=ben.dakin-norris@navtechradar.com \
--cc=dmalcolm@gcc.gnu.org \
--cc=fido_max@inbox.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).