From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-25
Date: Wed, 26 Feb 2014 08:00:15 -0300 [thread overview]
Message-ID: <530DC93F.3060205@zacarias.com.ar> (raw)
In-Reply-To: <87k3cigt81.fsf@dell.be.48ers.dk>
On 02/26/2014 05:42 AM, Peter Korsgaard wrote:
> > powerpc | mpd-0.18.7 | NOK | http://autobuild.buildroot.net/results/2862eba84c0922f19dbc2c7babcf15dbc137af93/
>
> C++ issue? Gustavo?
>
> ./src/fs/Path.hxx:61:29: error: invalid return type 'Path' of constexpr function 'static constexpr Path Path::Null()'
> ./src/fs/Path.hxx:69:47: error: invalid return type 'Path' of constexpr function 'static constexpr Path Path::FromFS(Path::const_pointer)'
Same toolchain as...
> > powerpc | sysklogd-1.5 | NOK | http://autobuild.buildroot.net/results/88d76be91d04a22dd2f1683396a172be085e1657/
>
> Internal compiler error. Thomas, how old is this ctng toolchain?
It's a 4.6.0 gcc, mpd requires at least 4.6 so the check passes, however
being a .0 i don't feel very confident about it not getting some bug
triggered.
It's probably worth upgrading to a new and internal toolchain for
e500v2, i regularly use it without issues and old toolchain components
where somewhat fragile about it.
> > powerpc | xlib_libXau-1.0.8 | NOK | http://autobuild.buildroot.net/results/f62f8e63082fdfb9a68c8b4e629e5a7fa02b3bba/
>
> Out of memory?
>
> configure: creating ./config.status
> ./config.status: fork: Cannot allocate memory
Very likely that the build machine was too busy at that moment.
> > bfin | zeromq-3.2.4 | NOK | http://autobuild.buildroot.net/results/0bf4621fad59fb0a42ae42b0a9d71e16ec49c617/
>
> atomics missings, perhaps we should mark it as !bfin?
We need the GCC version checks, this is another "too old gcc" issue
which is just a problem with the analog toolchain (should work with the
internal if the internal works, anybody tested that on real hardware?).
Regards.
next prev parent reply other threads:[~2014-02-26 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-25 Thomas Petazzoni
2014-02-26 8:42 ` Peter Korsgaard
2014-02-26 11:00 ` Gustavo Zacarias [this message]
2014-02-26 20:57 ` Thomas Petazzoni
2014-02-26 21:01 ` Peter Korsgaard
2014-02-26 21:04 ` Thomas Petazzoni
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=530DC93F.3060205@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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