autoconf usage question
Tue Oct 19 20:16:00 GMT 2004
Cross-compiling gnu (autoconfed packages) on the "clean" cygwin host system
recently worked well for me, while using the script (adopted from Kai
# PLEAS NOTE - THERE IS NO "make install" in this script ! ;-)
However, when I started to do "native" compiling on my "dirty used-to-be
target" ppc system,
(embedded diskless board, actually) running on "vanilla" Linux 2.6.8 (I am
building this system from scratch)
then I am having the problems I have described originally ("I know it's my
own damn fault" )
From: Robert Staven [mailto:email@example.com]
Sent: Tuesday, October 19, 2004 3:46 PM
To: Povolotsky, Alexander
Subject: Re: autoconf usage question
> The ./configure still picks the wrong compiler, fails the tests, pics
> incudes, etc ... .
> Also the "cache persistency" is the problem (IMHO) - if the options or env
> vars got changed - the "cached info"
> needs to be not used by "configure' ... (at least I would like to have
Had a problem in same direction. Deleting the 'config.cache' before
running ./configure helped. But you may have tried that.
I'm (trying to) use GNU autoconf/automake for cross compiling, but find
it hard to figure out how to do it... Not much info to find on the net.
I'm closing in, trying to figure out the libraries psrt now, but
documentation ist to good.. :)
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to firstname.lastname@example.org
More information about the crossgcc