Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] Configuring host-lzo fails
Date: Tue, 27 Jul 2010 23:33:09 +0200	[thread overview]
Message-ID: <201007272333.09640.PeterHuewe@gmx.de> (raw)

I've started a new thread, since it seems not related to avr32 in particular.

I'm using the atngw100_defconfig on my 64-bit gentoo system with a gcc 4.1.2

PH >> configure: loading cache /avr/buildroot/output/build/host-config.cache
PH >> configure: Configuring LZO 2.03
PH >> checking build system type... (cached) x86_64-unknown-linux-gnu
PH >> checking host system type... (cached) x86_64-unknown-linux-gnu
PH >> checking target system type... config.sub: missing argument
PH >> Try `config.sub --help' for more information.

TP > It sounds like the autoconf host-config.cache has been filled with an
TP > empty value for --target.
 
TP > Can you show the contents
TP > of /avr/buildroot/output/build/host-config.cache after the failure, and
TP> can you post the *full* build log somewhere ?

I've gzipped the whole build log (from a fresh git clone) and uploaded it to 
http://www.hs-augsburg.de/~phuewe/typescript2.gz (498K, unzipped 8,8Mb)

The contens of the host-config.cache can be found at
http://paste.pocoo.org/show/242433/


Thanks,
Peter

             reply	other threads:[~2010-07-27 21:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 21:33 Peter Hüwe [this message]
2010-07-27 21:56 ` [Buildroot] Configuring host-lzo fails Thomas Petazzoni
2010-07-27 22:20   ` Peter Huewe
2010-07-28  0:14     ` Peter Hüwe
2010-07-28 18:59       ` Ossy
2010-08-13 10:26 ` Thomas Petazzoni
2010-08-18 21:34   ` Ossy
2010-08-21 14:41     ` Ossy
2010-08-21 15:58       ` Ossy
2010-08-21 16:01       ` Thomas Petazzoni
2010-09-06  3:21         ` Khem Raj

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=201007272333.09640.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox