From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] nios2 : gcc 4.9.x buildroot toolchain broken
Date: Mon, 27 Jul 2015 22:48:16 +0200 [thread overview]
Message-ID: <20150727224816.29768dfd@free-electrons.com> (raw)
In-Reply-To: <CA+BsyQ6wmo0d4iZx_vREdZw9h=hQBg4vPOLwx9cwHAJGHhoGmA@mail.gmail.com>
Dear Brendan Heading,
On Mon, 27 Jul 2015 21:28:21 +0100, Brendan Heading wrote:
> While looking at the dmraid build bug on nios2 I noted that it is not
> possible to build a buildroot toolchain based on GCC 4.9.x for that
> platform.
>
> You can reproduce the problem using the following (one-line) defconfig :
>
> BR2_nios2=y
>
> I tested it against the commit : 5ccde01652bc41da325bf4c9a5abbf0031080784
>
> The error is as follows :
>
> =============
> ../../../libgcc/config/nios2/linux-atomic.c:23:24: fatal error:
> asm/unistd.h: No such file or directory
> #include <asm/unistd.h>
> ^
> compilation terminated.
> =============
>
> The problem only occurs on GCC 4.9.x. GCC 5.x builds fine.
>
> Someone already submitted a patch to fix this :
>
> http://lists.busybox.net/pipermail/buildroot/2015-February/119084.html
>
> The submitter promised to do some more work but it seems to have been left
> that way since last February.
>
> We can either :
> - disable GCC 4.9.x for nios2 (leaving 5.x as the only supported buildroot
> toolchain)
> - integrate & test the above patch
>
> What does everyone think ? Given that the above patch seems to be
> considered incomplete maybe we should disable nios2 4.9.x for now until the
> required additions have been submitted.
Hum, that's interesting. I indeed saw that gcc 4.9.3 was not building
properly for NIOS II. However, gcc 4.9.2 built fine for me. Look at
http://autobuild.buildroot.org/toolchains/tarballs/br-nios2-full-2015.05.tar.bz2:
it is a NIOS II gcc 4.9.2 toolchain generated by Buildroot.
So I don't really understand how Ezequiel fall into the problem of
<asm/unistd.h> with gcc 4.9.2. But I did indeed fall into this problem
with gcc 4.9.3.
Or maybe the problem is *not* gcc version related only, but also
related to the kernel headers version?
But in any case, Ezequiel's patch seems fine to me, I'll try to apply
something similar.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-27 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 20:28 [Buildroot] nios2 : gcc 4.9.x buildroot toolchain broken Brendan Heading
2015-07-27 20:48 ` Thomas Petazzoni [this message]
2015-08-01 16:15 ` Ezequiel Garcia
[not found] ` <55BCEF0B.5050101@free-electrons.com>
[not found] ` <55BDAF2C.1050301@gmail.com>
2015-08-03 15:48 ` Ezequiel Garcia
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=20150727224816.29768dfd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox