From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: buildroot@busybox.net
Subject: [Buildroot] Bash failing
Date: Wed, 30 Jul 2008 09:30:35 +0200 [thread overview]
Message-ID: <4890189B.3000502@cetrtapot.si> (raw)
In-Reply-To: <20080730012304.GA7254@cloud.net.au>
Hamish Moffatt wrote:
> On Tue, Jul 29, 2008 at 10:20:18PM +0100, Jonathan and Caroline Moore wrote:
>> Still no joy and it is all rather frustrating. Aren't these things
>> meant to "work out of the box"? Are you able to send me the .config
>> you have managed to get working and tell me the buildroot snapshot you
>> used please?
Config is attached.
Buildroot snapshot is r22940.
>
>> /opt/crosstool/gcc-4.1.0-glibc-2.3.2/arm-unknown-linux-gnu/lib/gcc/arm-unknown-linux-gnu/4.1.0/../../../../arm-unknown-linux-gnu/bin/ld:
>> cannot find -lcurses
>
> $(BASH_DIR)/$(BASH_BINARY): $(BASH_DIR)/.configured
> - $(MAKE1) CC=$(TARGET_CC) CC_FOR_BUILD="$(HOSTCC)" -C $(BASH_DIR)
> + $(MAKE1) CC=$(TARGET_CC) CC_FOR_BUILD="$(HOSTCC)" CFLAGS="-I$(STAGING_DIR)/usr/include" -C $(BASH_DIR)
>
> You probably also need an LDFLAGS="-L$(STAGING_DIR)/usr/lib" then.
>
Yes, apparently the LDFLAGS need to be fixed too.
> As to working "out of the box", you'd probably have more luck if you
> used the compiler that came out of the same box!
>
I agree with Hamish on this one.
As you can see buildroot can make its own toolchain and the possibility
to use external toolchain is not that much in use - meaning there are still
packages that might fail when compiled with external toolchain as we must
take into account compiler provided headers and libs.
It is almost impossible to make all toolchain/package/architecture combinations
work out of the box. Some combinations work without a glitch (wide usage),
while others need minor fixes, as in your case, to make things going on :)
>
>> make[3]: *** [info-recursive] Error 1
>
> That's weird since no error was printed before that. Can you debug it?
He probably ran the make twice.. Remove the binutils-* folders in toolchain
build_dir and rerun make.
Regards,
Hinko
--
?ETRTA POT, d.o.o., Kranj
Planina 3
4000 Kranj
Slovenia, Europe
Tel. +386 (0) 4 280 66 03
E-mail: hinko.kocevar at cetrtapot.si
Http: www.cetrtapot.si
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: buildroot.config
Url: http://busybox.net/lists/buildroot/attachments/20080730/501d5a2c/attachment.txt
prev parent reply other threads:[~2008-07-30 7:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 7:46 [Buildroot] Bash failing Jonathan and Caroline Moore
2008-07-28 8:42 ` Hinko Kocevar
2008-07-28 11:13 ` Jonathan and Caroline Moore
2008-07-28 12:50 ` Hinko Kocevar
2008-07-28 15:33 ` Jonathan and Caroline Moore
2008-07-29 7:34 ` Hinko Kocevar
2008-07-29 11:49 ` Jonathan and Caroline Moore
2008-07-29 12:14 ` Hinko Kocevar
2008-07-29 21:20 ` Jonathan and Caroline Moore
2008-07-30 1:23 ` Hamish Moffatt
2008-07-30 7:30 ` Hinko Kocevar [this message]
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=4890189B.3000502@cetrtapot.si \
--to=hinko.kocevar@cetrtapot.si \
--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