From: Ossy <ossy1980@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Configuring host-lzo fails
Date: Sat, 21 Aug 2010 17:58:09 +0200 [thread overview]
Message-ID: <4C6FF791.7040408@gmx.net> (raw)
In-Reply-To: <4C6FE59A.8020306@gmx.net>
Am 21.08.2010 16:41, schrieb Ossy:
> Am 18.08.2010 23:34, schrieb Ossy:
>> Am 13.08.2010 12:26, schrieb Thomas Petazzoni:
>>> This is fixed in my for-2010.08 branch, the specific commit being
>>> http://git.buildroot.net/~tpetazzoni/git/buildroot/commit/?h=for-2010.08&id=fee182d20d9b1876436c9673744ae6312a40e889.
>>>
>>>
>>>
>>> If you have the time to test this branch and report whether it also
>>> fixes the problem for you, it'd be nice.
>>
> > [host-zlib error]
>>
> The same patch applied, I ran into an error with expat today:
> configure: error: no acceptable ld found in $PATH
> make: ***
> [/home/ossy/buildroot/buildroot-dev/output/build/expat-2.0.1/.stamp_configured]
> Fehler 1
>
> After make flush; make the system build went on without problems.
>
The same whith which-2.20:
/buildroot/buildroot-dev/output/staging -DHAVE_CONFIG_H -I. -I.. -Os
-pipe -Os -mtune=arm926ej-s -march=armv5te -mabi=aapcs-linux
-msoft-float -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-D_FILE_OFFSET_BITS=64
-I/home/ossy/buildroot/buildroot-dev/output/staging/usr/include
-I/home/ossy/buildroot/buildroot-dev/output/staging/include -c shell.c
Unknown depmode none
make[3]: *** [tilde.o] Fehler 1
I had to make flush and rm -r output/build/which-2.20/
After flushing and removing the system build went on. Including which.
next prev parent reply other threads:[~2010-08-21 15:58 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
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 [this message]
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=4C6FF791.7040408@gmx.net \
--to=ossy1980@gmx.net \
--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