From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] GCC 4.6.x building : bootstraps and some other packages fail
Date: Thu, 2 Jun 2011 18:27:45 +0200 [thread overview]
Message-ID: <20110602182745.26ef31a6@surf> (raw)
In-Reply-To: <9E448A3C2A524B28B241DFDCA22CF9DC@JohanW7>
Hello,
On Thu, 2 Jun 2011 10:53:32 +0200
"Sagaert Johan" <sagaert.johan@skynet.be> wrote:
> /home/johan/buildroot-2011.05/output/host/usr/bin/../lib/gcc/arm-unknown-lin
> ux-uclibcgnueabi/4.6.0/../../../../arm-unknown-linux-uclibcgnueabi/bin/ld:
> section .text.startup loaded at [00200e7c,00200ea3] overlaps
> section .data loaded at [00200e7c,00200f3f]
This doesn't surprise me a lot. AT91Bootstrap is not an open community
project, so everybody keeps fixing the issues on their own without
contributing things back, and Atmel isn't really maintaining it
very actively. The upstream 1.16 version doesn't even build with EABI
toolchains, and Buildroot has a patch to fix this.
I'm afraid the build issue you had might be a problem in AT91Bootstrap
that you have to find and fix. Of course, we're interested by the patch.
Note that Atmel is working on a newer AT91Bootstrap version, available
as part of their Android4Sam initiative. This version, labeled "3" is
available at
ftp://ftp.linux4sam.org/pub/Android4SAM/9m10g45/v1.1/patches/bootstrap30.tar.gz.
I haven't tried it for now, but it uses kconfig for the configuration,
so it's probably a bit better than the 1.16 that is packaged in
Buildroot currently.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2011-06-02 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 8:53 [Buildroot] GCC 4.6.x building : bootstraps and some other packages fail Sagaert Johan
2011-06-02 16:27 ` Thomas Petazzoni [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=20110602182745.26ef31a6@surf \
--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