From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/boost: bump to version 1.59.0
Date: Mon, 14 Dec 2015 13:31:37 +0100 [thread overview]
Message-ID: <1450096297.5220.1.camel@embedded.rocks> (raw)
In-Reply-To: <20151213222827.027599c4@free-electrons.com>
Dear Thomas,
On So, 2015-12-13 at 22:28 +0100, Thomas Petazzoni wrote:
> Dear J?rg Krause,
>
> On Fri, 11 Dec 2015 14:57:57 +0100, J?rg Krause wrote:
> > Also:
> > * remove patch "gcc.jam compiler options fix" - merged upstream
> > * renumber patch "fix uclibc eventfd".
> >
> > Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
>
> I am not sure if it is related to the version bump or not, but boost
> is
> causing some build issues:
>
> ???http://autobuild.buildroot.org/?reason=boost-1.59.0
>
> Could you have a look ?
Actually, I already had two days ago :-)
From [1]:
<fenv.h> exists, but does not define FE_DIVBYZERO and co. Is this true
for all uclibc-based toolchains or is it dependent of the architecture?
[1]?http://lists.busybox.net/pipermail/buildroot/2015-December/146851.h
tml
prev parent reply other threads:[~2015-12-14 12:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 13:57 [Buildroot] [PATCH 1/3] package/boost: bump to version 1.59.0 Jörg Krause
2015-12-11 13:57 ` [Buildroot] [PATCH 2/3] package/boost: fix space tabs Jörg Krause
2015-12-11 14:48 ` Vicente Olivert Riera
2015-12-11 13:57 ` [Buildroot] [PATCH 3/3] package/boost: add library coroutine2 Jörg Krause
2015-12-11 15:08 ` Vicente Olivert Riera
2015-12-11 15:30 ` Thomas Petazzoni
2015-12-11 15:36 ` Vicente Olivert Riera
2015-12-11 15:46 ` Jörg Krause
2015-12-11 16:00 ` Jörg Krause
2015-12-11 16:18 ` Vicente Olivert Riera
2015-12-11 14:45 ` [Buildroot] [PATCH 1/3] package/boost: bump to version 1.59.0 Vicente Olivert Riera
2015-12-12 12:54 ` Thomas Petazzoni
2015-12-13 21:28 ` Thomas Petazzoni
2015-12-14 12:31 ` 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=1450096297.5220.1.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