Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] zeromq: fix build on m68k_cf
Date: Tue, 21 Aug 2018 08:53:56 +0200	[thread overview]
Message-ID: <87ftz82osb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180820230228.07ebf70f@windsurf> (Thomas Petazzoni's message of "Mon, 20 Aug 2018 23:02:28 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > Hello,
 > On Mon, 20 Aug 2018 18:59:29 +0200, Fabrice Fontaine wrote:

 >> +# Internal error, aborting at dwarf2cfi.c:2752 in connect_traces
 >> +# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58864
 >> +ifeq ($(BR2_m68k_cf),y)
 >> +ZEROMQ_CONF_OPTS += CXXFLAGS="$(TARGET_CXXFLAGS) -fno-defer-pop"
 >> +endif

 > I've applied, but what bothers me is that we will never notice if/when
 > this workaround can be removed. Perhaps we should make such workarounds
 > depend on the gcc version, like this:

 > ifeq ($(BR2_TOOLCHAIN_GCC_AT_LEAST_9):$(BR2_m68k_cf),:y)
 > ...
 > endif

 > This way, when we start using gcc 9.x, the workaround is no longer
 > applied. Either the bug is fixed, and we never see a build failure
 > again. Or the bug is not fixed, we noticed via autobuilder failure, and
 > extend the workaround to gcc 10.x.

 > Not sure what others think about this. OTOH, this is just about m68k
 > coldfire, maybe we don't care. But it's code that would probably stay
 > forever in BR.

I agree that it isn't super important here, but I like it! It's a great
way to verify if all the various workarounds are still needed when the
gcc version is bumped, and this only happens fairly rarely - So the
extra noise from this is pretty low.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2018-08-21  6:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20 16:59 [Buildroot] [PATCH 1/1] zeromq: fix build on m68k_cf Fabrice Fontaine
2018-08-20 21:02 ` Thomas Petazzoni
2018-08-21  6:53   ` Peter Korsgaard [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=87ftz82osb.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox