From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 is broken (toolchain)
Date: Thu, 22 Jul 2010 04:57:23 +0200 [thread overview]
Message-ID: <201007220457.24834.PeterHuewe@gmx.de> (raw)
In-Reply-To: <AANLkTikKS2AppP8zpPudDFbKvchDZvlpfQeTb-TKKvT2@mail.gmail.com>
Peter > I'll have a look into it - currently the code still compiles :)
Thiago > What do you mean it still compiles?
This just means that my machine is a little bit slow and it takes awhile to
compile buildroot.
Thiago > I get an error building the toolchain, something along the lines of:
Thiago > make[3]: *** Waiting for unfinished jobs....
Thiago > /root/buildroot-head/output/toolchain/gcc-4.2.2-avr32-2.1.5-
final/./gcc/as:
Thiago > line 2: exec: --: invalid option
Thiago> exec: usage: exec [-cl] [-a name] [command [arguments ...]]
[redirection
Thiago > ...] make[3]: *** [crtbeginS.o] Error 1
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 :)
Thanks,
Peter
next prev parent reply other threads:[~2010-07-22 2:57 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 [this message]
2010-07-22 12:17 ` Thomas Petazzoni
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=201007220457.24834.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.