This is the mail archive of the crossgcc@sourceware.org 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] |
On Tue, 2005-09-20 at 06:16 +0000, David Karlton <dkarlton@themediamall.com> wrote: > I'm trying to build crosstool-0.38 on a number of linux installation > (Suse 9.1, Fedora Core 2), and am having trouble with Fedora. Notably, > it is telling me that gcc 4.0.0 is too "old", when trying to build > gcc-3.3.4-glibc-2.3.2 for mipsel. > > On my Suse installation, I have gcc 3.3.3. Is the fact that it > complains about 4.0.0 on Fedora a bug in the build routine? Something I > can fix? > > dk > > ********************************* > > checking build system type... i686-pc-linux-gnu > checking host system type... mipsel-unknown-linux-gnu > checking sysdep dirs... sysdeps/mips/elf sysdeps/unix/sysv/linux/mips > sysdeps/unix/sysv/linux sysdeps/gnu sysdeps/unix/common > sysdeps/unix/mman sysdeps/unix/inet sysdeps/unix/sysv sysdeps/unix/mips > sysdeps/unix sysdeps/posix sysdeps/mips/mipsel sysdeps/mips/fpu > sysdeps/mips sysdeps/wordsize-32 sysdeps/ieee754/flt-32 > sysdeps/ieee754/dbl-64 sysdeps/ieee754 sysdeps/generic/elf sysdeps/generic > checking for a BSD-compatible install... /usr/bin/install -c > checking whether ln -s works... yes > checking for pwd... /bin/pwd > checking for mipsel-unknown-linux-gnu-gcc... gcc > checking version of gcc... 4.0.0, bad > checking for gnumake... no > checking for gmake... gmake > checking version of gmake... 3.80, ok > configure: error: > *** These critical programs are missing or too old: gcc > *** Check the INSTALL file for required versions. > I have had the same problem. What I found was that the glibc configure script was testing for a version of gcc 3.2.* or later. It does not test for a major number above 3 so the test fails. I do not know where this test is initiated, but once you have reached that point you can patch the configure script and run demo-*.sh with the --nounpack option added to your desired toolchain build. This patch worked for me: --- configure.orig 2005-09-19 21:31:45.000000000 -0400 +++ configure 2005-09-19 21:32:13.000000000 -0400 @@ -2274,6 +2274,8 @@ '') ac_prog_version="v. ?.??, bad"; ac_verc_fail=yes;; 3.[2-9]*) ac_prog_version="$ac_prog_version, ok"; ac_verc_fail=no;; + 4.*) + ac_prog_version="$ac_prog_version, ok"; ac_verc_fail=no;; *) ac_prog_version="$ac_prog_version, bad"; ac_verc_fail=yes;; esac I hope that this helps. Good Luck. -Mike Joyce ------ 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] |