From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ptpd2: fix bfin compile by avoiding gcc bug
Date: Tue, 22 Nov 2016 11:16:16 +0100 [thread overview]
Message-ID: <20161122111616.4cdfdd67@free-electrons.com> (raw)
In-Reply-To: <20161122101219.GT27313@waldemar-brodkorb.de>
Hello,
On Tue, 22 Nov 2016 11:12:20 +0100, Waldemar Brodkorb wrote:
> > However, I continue to dislike such hacks: when the problem gets fixed
> > by gcc, how will we notice?
>
> Either when we get notice that the PR is closed, this time I need to
> create one. But we have similar issues where we already have PR's.
> Or we check when a new gcc release come out, if the results from
> "grep bfin package/*/*mk" are still required.
Maybe we need to have some kind of convention of a specific string to
include in the comment on such hacks, in order to more easily grep?
Like:
# Workaround gcc-prXYZ
or
# Workaround binutils-prXYZ
This way, we can grep for "gcc-pr" and "binutils-pr" and easily check
the status of those PRs.
> I think better then never ending autobuild failures.
For sure, I'm not claiming we should keep things as-is. It's good to
add temporary hacks, but it's also good to think about how we can at
some point remove those hacks.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-11-22 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 18:32 [Buildroot] [PATCH] ptpd2: fix bfin compile by avoiding gcc bug Waldemar Brodkorb
2016-11-21 21:04 ` Thomas Petazzoni
2016-11-22 10:12 ` Waldemar Brodkorb
2016-11-22 10:16 ` Thomas Petazzoni [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=20161122111616.4cdfdd67@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.