Yuri Karlsbrun wrote:
> Hi,
>
> I build bash v3.1 for cross-target. I configured bash like this:
>
> CC=<my_target_gcc> AR=<my_target_ar> RANLIB=<my_target_ranlib>
> <bash-3.1_src/configure>/configure --host=<my_target> --target=<my_target>
> --build=i686-pc-linux-gnu --disable-nls --prefix=<my_install_dir>
>
> 1. To complete build I had to comment out running test on cross-target.
The usual solution for this is to create a config.cache file with the
correct values for the cache variables in question.
> 2. Build picks up headers from /usr/include, not from the directory where
> <my_target_gcc> is installed. I have no problem building applications for my
> target using cross-target tool chain.
Bash doesn't specify /usr/include at all. Isn't it the responsibility
of the compiler to choose an appropriate set of default include
directories?
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live Strong. No day but today.
Chet Ramey, ITS, CWRU [EMAIL PROTECTED] http://cnswww.cns.cwru.edu/~chet/
_______________________________________________
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
