From: MikeW <mw_phil@yahoo.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Impossible to build EABI ARM gcc toolchain using Buildroot ?
Date: Mon, 18 Dec 2006 11:37:11 +0000 (UTC) [thread overview]
Message-ID: <loom.20061218T123140-410@post.gmane.org> (raw)
In-Reply-To: loom.20061214T103502-915@post.gmane.org
MikeW <mw_phil@...> writes:
>
> Pavel Roskin <proski <at> ...> writes:
>
> > Maybe you can fix it. You can try another compiler.
>
> Unfortunately, Buldroot gcc-4.1.1 which includes ARM EABI support won't build
> the 2.6.10 kernel we are using - fails in the get_user macro in uaccess.h.
>
> Patch that, something else breaks in a similar way due to the compiler
> breaking code that worked under gcc-3.4.x (it needs a switch to turn this off!)
>
> The joys of bazaar development - grrr !
>
> Regards,
> MikeW
>
Looks like the only 3.4.x version of GCC is the one from CodeSourcery,
http://www.codesourcery.com/gnu_toolchains/arm/releases.html
I think one of the older ones is derived from a 3.4.x GCC.
Was considering doing a Buildroot config.in patch to get the tar.bz2 file from
the CS website, but unfortunately the files are returned in response
to a form submission :(
MikeW
next prev parent reply other threads:[~2006-12-18 11:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 13:25 [Buildroot] Impossible to build EABI ARM gcc toolchain using Buildroot ? MikeW
2006-11-30 1:07 ` Pavel Roskin
2006-11-30 11:14 ` MikeW
2006-12-01 8:11 ` Pavel Roskin
2006-12-01 10:13 ` MikeW
2006-12-01 10:28 ` MikeW
2006-12-13 12:08 ` MikeW
2006-12-13 19:22 ` [Buildroot] Impossible to build EABI ARM gcc toolchain?using?Buildroot ? Bernhard Fischer
2006-12-14 9:40 ` [Buildroot] Impossible to build EABI ARM gcc toolchain using Buildroot ? MikeW
2006-12-18 11:37 ` MikeW [this message]
2006-12-18 12:15 ` [Buildroot] Impossible to build EABI ARM gcc toolchain?using?Buildroot ? Bernhard Fischer
2006-11-30 10:20 ` [Buildroot] Impossible to build EABI ARM gcc toolchain using Buildroot ? + MikeW
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=loom.20061218T123140-410@post.gmane.org \
--to=mw_phil@yahoo.co.uk \
--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