Re: problem - ia64 gcc-3.2.3-glibc-2.3.2 cross compile using crosstool

[Dan Kegel <dank at kegel dot com>]

On 1/18/06, Peter Leggett <P.Leggett@gre.ac.uk> wrote:
> My first attempt was to attempt to compile gcc-3.2.3-glibc-2.3.2 on the
> local ia64 box directly using an adapted demo-ia64.sh
> ...
> checking version of gcc... 2.96, bad
> checking for gnumake... no
> checking for gmake... gmake
> checking version of gmake... 3.79.1, ok
> configure: error:
> *** These critical programs are missing or too old: gcc

That error happened during configure of glibc-2.3.2.
It's a bogus error, I think, because we're only using
the host's CC for installing glibc's headers.
So there are two ways to go:
1) hack glibc's configure script to remove that check, e.g.

--- glibc-2.3.2/configure.old   Wed Jan 18 08:39:44 2006
+++ glibc-2.3.2/configure       Wed Jan 18 08:40:25 2006
@@ -2272,6 +2272,8 @@
   ac_prog_version=`$CC -v 2>&1 | sed -n 's/^.*version
\([egcygnustpi-]*[0-9.]*\).*$/\1/p'`
   case $ac_prog_version in
     '') ac_prog_version="v. ?.??, bad"; ac_verc_fail=yes;;
+    2.9*)
+       ac_prog_version="$ac_prog_version, ok, hope you know what you
are doing"; ac_verc_fail=no;;
     3.[2-9]*)
        ac_prog_version="$ac_prog_version, ok"; ac_verc_fail=no;;
     *) ac_prog_version="$ac_prog_version, bad"; ac_verc_fail=yes;;

or install a local native copy of gcc-3.2.3 and use that to build
the toolchain.  (That's easy, just download the gnu tarball
and do the usual configure/make/make install thing.  Since you
don't have root, you'd need to use --prefix=$HOME/mygcc323 or something.)
- Dan

--
Wine for Windows ISVs: http://kegel.com/wine/isv

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