From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] bash fails to compile with git tree
Date: Mon, 31 Aug 2009 10:15:47 +0200 [thread overview]
Message-ID: <87pracqtzg.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <159a01660908280221m79835c8dy88aba6ce39dc4bff@mail.gmail.com> (Daniele Salvatore Albano's message of "Fri\, 28 Aug 2009 11\:21\:13 +0200")
>>>>> "Daniele" == Daniele Salvatore Albano <d.albano@gmail.com> writes:
Hi,
Daniele> have someone tried to compile bash? Yesterday, trying to fix
Daniele> my buildroot to send patches i moved my tree and cloned the
Daniele> head to get a working one (i got some problems with git) but
Daniele> when i tried to compile my root system, without applying any
Daniele> patches i done (i was just waiting to get errors to apply
Daniele> patches), bash failed to compile with a strange reason:
Daniele> missing termcap.h
Daniele> Checking ncurses and bash make files seems all ok, and making
Daniele> a diff with my old tree showed no differences. Toolchain works
Daniele> perfectly because i can build mi initrd (i use two separate br
Daniele> trees) without any problem and that br2 is from git and is up
Daniele> to date too. I don't build bash on my initrd, only busybox
Daniele> with few stuff.
Daniele> I can't send my .config, i'm at work, when i'll get at home
Daniele> i'll send it, however someone got problems building bash?
Is this with an external toolchain? I just did a quick test build on
i686 with the normal internal toolchain and bash builds without problems
here.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-08-31 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 9:21 [Buildroot] bash fails to compile with git tree Daniele Salvatore Albano
2009-08-28 18:05 ` Daniele Salvatore Albano
2009-08-31 8:15 ` Peter Korsgaard [this message]
2009-08-31 10:39 ` Sven Neumann
2009-09-01 5:36 ` Peter Korsgaard
2009-09-01 15:07 ` Sven Neumann
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=87pracqtzg.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.