On Thu, May 24, 2001 at 12:44:08PM +0530, pradeep wrote:
> For glibc I did
> CC=arm-linux-gcc
> path set
> I configured it , and did some manipulation now
> I am not able configure it as it is giving the following
> error
> now it is configured as cross compiler, how to bring
> back to
> just a native one ie gcc
Just rm config.cache and retry.
> ../glibc-2.2.2/configure arm-linuxlib --build=i586-linux
^^^^^^^^^^^^
This is wrong. The target architecture arm-linuxlib doesn't exists, you
want arm-linux.
> --prefix=/home/pradeep/armtool --enable-add-ons
> loading cache ./config.cache
> checking host system type... arm-unknown-linux-gnulib
> checking sysdep dirs... sysdeps/arm/elf
> linuxthreads/sysdeps/unix/sysv/linux linuxthreads/sysdeps/pthread
> linuxthreads/sysdeps/unix/sysv linuxthreads/sysdeps/unix
> linuxthreads/sysdeps/arm sysdeps/unix/sysv/linux/arm
> sysdeps/unix/sysv/linux sysdeps/gnu sysdeps/unix/common
> sysdeps/unix/mman sysdeps/unix/inet sysdeps/unix/sysv sysdeps/unix/arm
> sysdeps/unix sysdeps/posix sysdeps/arm/fpu sysdeps/arm
> 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 build system type... i586-pc-linux-gnu
> checking for arm-linuxlib-gcc... no
^^^^^^^^^^^^^^^^
And because you did it wrong, the configure script can't find the
compiler.
> checking for arm-linuxlib-cc... no
> checking for gnumake... no
> checking for gmake... gmake
> checking version of gmake... 3.79.1, ok
> checking for gnumsgfmt... no
> checking for gmsgfmt... no
> checking for msgfmt... msgfmt
> checking version of msgfmt... 0.10.35, ok
> checking for makeinfo... makeinfo
> checking version of makeinfo... 4.0, ok
> checking for gsed... no
> checking for sed... sed
> checking version of sed... 3.02, ok
> checking whether the C compiler ( ) works... no
> checking whether the C compiler ( ) is a cross-compiler... (cached) yes
^^
And because the configure script can't find a compiler, it can't test
if it is a cross-compiler.
> checking whether we are using GNU C... no
> configure: error: GNU libc must be compiled using GNU CC
^^^^^
And because the configure script can't find a cross compiler, it also
can't test if it is a GNU C compiler.
> [root@ws120 arm-linuxlib]# make
> make: *** No targets specified and no makefile found. Stop.
And because the configure script can't find a GNU C cross compiler, it
can't continue and doesn't make a Makefile. Error messages are usually
quite clear.
But why do you bother building a toolchain when there are numerous
precompiled toolchains available? See the archive of this list for
locations. Or if you are really desparate and want to build a toolchain
yourself check out:
http://www.armlinux.org/docs/toolchain/
And follow the instructions *exactly*.
Erik
--
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031, 2600 GA Delft, The Netherlands
Phone: +31-15-2783635 Fax: +31-15-2781843 Email: [EMAIL PROTECTED]
WWW: http://www-ict.its.tudelft.nl/~erik/
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
