This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: autoconf usage question


Povolotsky, Alexander wrote:
I noticed that, possibly due to "misconfigured" (non-standard,
non-conventional) placement of the s/w (compiler, binutils, libraries, includes) on my system, which has both
native and cross-compiler gcc,
unless I use the shell script with env vars, pointing to the right
"full-path",
the ./configure does not "guess" correctly that "user wants" the native
compiler to be used
(rather then cross-compiler), even with the "options hint",
having all 3 options (--build, --host and --target) being all set pointing
to the "native" architecture ...



I had a problem with an elderly config.guess in ISC's DHCPCD which prevented cross-compiling. We don't happen to use that package any more, but at the time I worked around it (successfully) by just dropping in a newer config.guess and config.sub. Like this:


tar -zxf dhcpcd-1.3.22-pl4.tar.gz
cd dhcpcd-1.3.22-pl4/
cp /usr/share/automake-1.8/config.{guess,sub} .
./configure .... etc.

--
Simon Poole
www.appliancestudio.com

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]