From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 is broken (toolchain)
Date: Thu, 22 Jul 2010 14:17:15 +0200 [thread overview]
Message-ID: <20100722141715.7bbc4963@surf> (raw)
In-Reply-To: <201007220457.24834.PeterHuewe@gmx.de>
Hello,
On Thu, 22 Jul 2010 04:57:23 +0200
Peter H?we <PeterHuewe@gmx.de> wrote:
> Yeah - I can reproduce this issue.
>
> However I got another error first (something like avr32-.....-ar:
> command not found). But I got the same error after adding the
> AR_FOR_BUILD="$(HOSTAR)" \
> AR_FOR_TARGET="$(TARGET_AR)" \
> lines again.
>
> Currently I'm trying compiling a version of BR with and without the
> changes in Thomas' commit - tomorrow I'll compare the output :)
FWIW, I can also reproduce the issue. It seems to be due to the fact
that the --prefix location is not writable (since it's /usr). See
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32101#c4.
So, I've cooked the attached patch, which allows the toolchain to
build, but the toolchain fails when compiling Busybox with messages
such as :
dc.c:(.text+0x10c): relocation truncated to fit: R_AVR32_22H_PCREL
against symbol `__avr32_f64_to_u32' defined in .text section
in /home/test/issue/old-br/buildroot/output/staging/usr/lib/gcc/avr32-unknown-linux-uclibc/4.2.2/libgcc.a(_avr32_f64_to_s32.o)
I don't yet know what is happening.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: toolchain-fix.patch
Type: text/x-patch
Size: 2623 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100722/10832c77/attachment.bin>
next prev parent reply other threads:[~2010-07-22 12:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 22:02 [Buildroot] AVR32 is broken (toolchain) Thiago A. Corrêa
2010-07-22 1:52 ` Peter Hüwe
2010-07-22 2:29 ` Thiago A. Corrêa
2010-07-22 2:57 ` Peter Hüwe
2010-07-22 12:17 ` Thomas Petazzoni [this message]
2010-07-22 15:10 ` Thomas Petazzoni
2010-07-22 16:35 ` Thiago A. Corrêa
2010-07-23 19:12 ` Thiago A. Corrêa
2010-07-23 21:18 ` Thomas Petazzoni
2010-07-27 1:14 ` Peter Hüwe
2010-07-27 15:17 ` Thomas Petazzoni
2010-07-27 20:39 ` Peter Hüwe
2010-07-31 0:50 ` Bjørn Forsman
2010-07-31 4:58 ` Thiago A. Corrêa
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=20100722141715.7bbc4963@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