From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: buildroot@busybox.net
Subject: [Buildroot] Bash failing
Date: Tue, 29 Jul 2008 09:34:07 +0200 [thread overview]
Message-ID: <488EC7EF.4090203@cetrtapot.si> (raw)
In-Reply-To: <8bf7d05b0807280833x7cace636xa2b41176d306b6be@mail.gmail.com>
Jonathan and Caroline Moore wrote:
> Below are the last few lines of output after make and the results of
> the find command.
>
> The entire log generated by the command
> make >log 2>&1 can be downloaded here
> http://jandcmoore.googlepages.com/buildroot20080727.make.log.txt
I see you are using external (precompiled) toolchain, right? I don't know
if that might be the case for missing header locations...
The compilation lines that fail are the same in my and your case,
but you are using libc based instead of uclibc based compiler and
I suspect that my compiler looks for headers in STAGING_DIR/usr/include
without the -I switch added.
Can we see the output of failed compile with '-v' option added?
Here is mine:
$ cd /tmp//buildroot/build_arm/bash-3.2/lib/readline
/tmp/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-gcc -c -DHAVE_CONFIG_H -DSHELL -I. -I/tmp/buildroot/build_arm/bash-3.2 -I../.. -I../../lib -g -O2 display.c -v
Using built-in specs.
Target: arm-linux-uclibc
Configured with: /tmp/buildroot/toolchain_build_arm/gcc-4.2.4/configure --prefix=/usr --build=i386-pc-linux-gnu --host=i386-pc-linux-gnu --target=arm-linux-uclibc --enable-languages=c --with-sysroot=/tmp/buildroot/build_arm/staging_dir --with-build-time-tools=/tmp/buildroot/build_arm/staging_dir/usr/arm-linux-uclibc/bin --disable-__cxa_atexit --enable-target-optspace --with-gnu-ld --enable-shared --with-gmp=/tmp/buildroot/toolchain_build_arm/gmp --with-mpfr=/tmp/buildroot/toolchain_build_arm/mpfr --disable-nls --enable-threads --disable-multilib
Thread model: posix
gcc version 4.2.4
/tmp/buildroot/build_arm/staging_dir/usr/bin/../libexec/gcc/arm-linux-uclibc/4.2.4/cc1 -quiet -v -I. -I/tmp/buildroot/build_arm/bash-3.2 -I../.. -I../../lib -iprefix /tmp/buildroot/build_arm/staging_dir/usr/bin/../lib/gcc/arm-linux-uclibc/4.2.4/ -DHAVE_CONFIG_H -DSHELL display.c -quiet -dumpbase display.c -auxbase display -g -O2 -version -o /tmp/ccQNsOEA.s
ignoring nonexistent directory "/tmp/buildroot/build_arm/staging_dir/usr/bin/../lib/gcc/arm-linux-uclibc/4.2.4/../../../../arm-linux-uclibc/include"
ignoring nonexistent directory "/tmp/buildroot/build_arm/staging_dir/usr/local/include"
ignoring nonexistent directory "/usr/lib/gcc/arm-linux-uclibc/4.2.4/include"
ignoring nonexistent directory "/usr/lib/gcc/../../arm-linux-uclibc/include"
ignoring duplicate directory "../.."
#include "..." search starts here:
#include <...> search starts here:
.
/tmp/buildroot/build_arm/bash-3.2
../../lib
/tmp/buildroot/build_arm/staging_dir/usr/bin/../lib/gcc/arm-linux-uclibc/4.2.4/include
/tmp/buildroot/build_arm/staging_dir/usr/include
End of search list.
GNU C version 4.2.4 (arm-linux-uclibc)
compiled by GNU C version 4.1.2 (Gentoo 4.1.2 p1.1).
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: f2f3758be9e267946c957c7de1fa7038
display.c: In function 'rl_character_len':
display.c:1961: warning: comparison is always true due to limited range of data type
/tmp/buildroot/build_arm/staging_dir/usr/bin/../lib/gcc/arm-linux-uclibc/4.2.4/../../../../arm-linux-uclibc/bin/as -o display.o /tmp/ccQNsOEA.s
It can be seen that my compiler looks in '/tmp/buildroot/build_arm/staging_dir/usr/include' for headers,
where termcap.h is located - does compiler search there too?
>
> Hinko can you send me your buildroot config file please? Mine is here
> http://jandcmoore.googlepages.com/config
>
Here you go:
http://hinkocevar.googlepages.com/config
>
> WS867:Mon 28:1614:buildroot-20080727:$ !find
> find build_arm -name termcap.h
> build_arm/ncurses-5.6/include/termcap.h
> build_arm/staging_dir/usr/include/termcap.h
> build_arm/bash-3.2/lib/termcap/termcap.h
>
Fine, the header seems to be in place. But does the compiler know where to look?
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-29 7:34 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 [this message]
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=488EC7EF.4090203@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