Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Huewe <PeterHuewe@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] Configuring host-lzo fails
Date: Wed, 28 Jul 2010 00:20:05 +0200	[thread overview]
Message-ID: <201007280020.05811.PeterHuewe@gmx.de> (raw)
In-Reply-To: <20100727235653.0d2215eb@surf>

Hi Thomas, 
> I was also able to reproduce the issue. 
good - makes it easier to track down ;)

> Thanks. As I could reproduce, I've started to investigate the problem.
> I've summarized my findings at
> http://free-electrons.com/~thomas/pub/autoconf-issue.txt, but I don't
> have a clear solution yet.
> 
> As a temporary fix, you can probably try something like :
> 
> HOST_LZO_CONF_OPT = --target=$(GNU_HOST_NAME)
> 
> in package/lzo/lzo.mk.
> 

I tried your temporary and it works - however I made following observation.
0)  rm -rf /buildroot/output/build/host-lzo-2.03/  buildroot/output/build/host-config.cache
1) Add HOST_LZO_CONF_OPT = --target=$(GNU_HOST_NAME) to package/lzo/lzo.mk
2) make
--> host lzo builds fine

3) rm -rf /buildroot/output/build/host-lzo-2.03/  buildroot/output/build/host-config.cache
4) remove HOST_LZO_CONF_OPT = --target=$(GNU_HOST_NAME) from package/lzo/lzo.mk
5) make
--> host lzo builds perfectly fine too!

Any Ideas? 
Since I've removed the cache, we don't have a cached value here.


Thanks,
Peter


btw.: the german umlaut in my name (?) is usually converted to ue, strange german language thing ;)

  reply	other threads:[~2010-07-27 22:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 21:33 [Buildroot] Configuring host-lzo fails Peter Hüwe
2010-07-27 21:56 ` Thomas Petazzoni
2010-07-27 22:20   ` Peter Huewe [this message]
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=201007280020.05811.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