hmm ... seems my e-mail client crashed when i sent the last message ...
On Monday 13 February 2006 19:31, Yuri Karlsbrun wrote:
> You just cannot execute cross-compiled code on native platform...
yes, i know that, that isnt what i asked you
> Also mksignames utility is built using native headers
On Monday 13 February 2006 19:31, Yuri Karlsbrun wrote:
> You just cannot execute cross-compiled code on native platform...
yes, i know that, that isnt what i asked you
> Also mksignames utility is built using native headers (from /usr/include),
> so signal name translation is incorrect for cross
> -Original Message-
> From: Mike Frysinger [mailto:[EMAIL PROTECTED]
> > > 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.
>
>
On Monday 13 February 2006 15:40, Chet Ramey wrote:
> Yuri Karlsbrun wrote:
> > I build bash v3.1 for cross-target. I configured bash like this:
> >
> > CC= AR= RANLIB=
> > /configure --host=
> > --target= --build=i686-pc-linux-gnu --disable-nls
> > --prefix=
> >
> > 1. To complete build I had to c
> 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?
>
When I build other applications for my target, I have no problems with
headers. When I explicitly included header's path
(CPPFLAGS="-I"), it
Yuri Karlsbrun wrote:
> Hi,
>
> I build bash v3.1 for cross-target. I configured bash like this:
>
> CC= AR= RANLIB=
> /configure --host= --target=
> --build=i686-pc-linux-gnu --disable-nls --prefix=
>
> 1. To complete build I had to comment out running test on cross-target.
The usual solution
