From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: buildroot@busybox.net
Subject: [Buildroot] Bash failing
Date: Mon, 28 Jul 2008 14:50:29 +0200 [thread overview]
Message-ID: <488DC095.7000303@cetrtapot.si> (raw)
In-Reply-To: <8bf7d05b0807280413t58506a27jcfcf36ae301de559@mail.gmail.com>
Jonathan and Caroline Moore wrote:
> OK I guess I need some more help.
>
> I thought buildroot took care of these details or am I meant to do
> something before typing make?
It should. ncurses package is responsible for termcap.h. I've just built
the bash for i686 here, and haven't stumbled across your problem.
>
> Would it help if I attached some of the files?
Show us the output of:
/buildroot $ find build_<arch> -name termcap.h
Here, for i686 it is:
/buildroot $ find build_i686 -name termcap.h
build_i686/ncurses-5.6/include/termcap.h
build_i686/bash-3.2/lib/termcap/termcap.h
build_i686/staging_dir/usr/include/termcap.h
.. adn for generic arm:
/buildroot $ find build_arm -name termcap.h
build_arm/ncurses-5.6/include/termcap.h
build_arm/bash-3.2/lib/termcap/termcap.h
build_arm/staging_dir/usr/include/termcap.h
The last line one is the one I suppose you are missing although I can't see why!?
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 prev parent reply other threads:[~2008-07-28 12:50 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 [this message]
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
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=488DC095.7000303@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