Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] boost: add patch to fix test of FPE support
Date: Sun, 12 Mar 2017 13:14:04 +0100	[thread overview]
Message-ID: <1489320844.14721.4.camel@embedded.rocks> (raw)
In-Reply-To: <20170312113117.6532fae5@free-electrons.com>

On Sun, 2017-03-12 at 11:31 +0100, Thomas Petazzoni wrote:
> Hello,
> 
> On Sat, 11 Mar 2017 21:33:37 +0100, J?rg Krause wrote:
> > We recently bumped boost from version 1.61.0 to 1.63.0.
> > 
> > Upstream has updated the handling of FPE support in 1.63.0
> > resulting in build
> > errors for some architectures, like SH4 and OpenRISC, which were
> > build
> > successfully with 1.61.0.
> 
> Sorry, I'm only seeing this patch now. I reverted the 1.63.0 bump of
> Boost just a few minutes ago.

All build errors from the autobuilders are related to the issue covered
by the patch.

> So, could you cook a new patch that bumps boost, test it with the
> test-pkg utility (with all boost sub-options enabled), and if it
> succeeds, submit it?

I only enabled the boost-test module, as to many toolchains are skipped
otherwise. None has failed :-)

> Thanks a lot for your work. Bumping boost has never been very easy :-
> /

I'll resubmit the commit with the patch from upstream included.

J?rg

      reply	other threads:[~2017-03-12 12:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-11 20:33 [Buildroot] [PATCH] boost: add patch to fix test of FPE support Jörg Krause
2017-03-12 10:31 ` Thomas Petazzoni
2017-03-12 12:14   ` Jörg Krause [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=1489320844.14721.4.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --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