From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 is broken (toolchain)
Date: Tue, 27 Jul 2010 17:17:54 +0200 [thread overview]
Message-ID: <20100727171754.59da191e@surf> (raw)
In-Reply-To: <201007270314.15113.PeterHuewe@gmx.de>
Hello Peter,
On Tue, 27 Jul 2010 03:14:14 +0200
Peter H?we <PeterHuewe@gmx.de> wrote:
> I just tried to compile the atngw100_defconfig using your patch and
> the latest git repo but unfortunately it fails while building host-lzo
>
> >>> host-lzo 2.03 Configuring
host-lzo is built for the host, so it's quite unlikely that any AVR32
change can have an impact on it.
> configure: loading cache /avr/buildroot/output/build/host-config.cache
> configure: Configuring LZO 2.03
> checking build system type... (cached) x86_64-unknown-linux-gnu
> checking host system type... (cached) x86_64-unknown-linux-gnu
> checking target system type... config.sub: missing argument
> Try `config.sub --help' for more information.
It sounds like the autoconf host-config.cache has been filled with an
empty value for --target.
Can you show the contents
of /avr/buildroot/output/build/host-config.cache after the failure, and
can you post the *full* build log somewhere ?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-07-27 15: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
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 [this message]
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=20100727171754.59da191e@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