This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
building
- From: Peter T Greening <peteman at math dot unm dot edu>
- To: gcc at gcc dot gnu dot org
- Date: Wed, 18 Jun 2003 17:09:25 -0600
- Subject: building
- Reply-to: help at math dot unm dot edu
Hi, I am trying to build gcc 3.3 on a linux redhat NFS environment. The
machine I am trying to build on is a redhat 7.3 running on an athlon(mp), and
almost all of the NFS mounted software was built on 7.3 machines. The run
configure as folllows:"./configure --prefix=/usr/local/pkg/gcc/gcc-3.3".
While building gnu c compiler, it returns the following error:
Configuring gcc...
loading cache ../config.cache
checking LIBRARY_PATH variable... ok
checking GCC_EXEC_PREFIX variable... ok
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for gcc... (cached) gcc
checking whether the C compiler (gcc -g -O2 ) works... yes
checking whether the C compiler (gcc -g -O2 ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking whether gcc and cc understand -c and -o together... (cached) yes
checking for gnatbind... no
checking for compiler driver that understands Ada... no
checking whether gcc accepts -Wno-long-long... yes
checking how to run the C preprocessor... /usr/local/bin/g++
checking for inline... (cached) inline
checking for volatile... yes
checking for long double... yes
checking for long long int... yes
checking for __int64... no
checking for built-in _Bool... yes
checking size of short... 2
checking size of int... 4
checking size of long... 4
checking size of long long... 8
checking execution character set... unknown
configure: error: *** Cannot determine host character set.
Configure in /usr/local/src/gcc/gcc-3.3/gcc failed, exiting.
what to do, please help. Thanks in advance
--
Pete Greening
student system administrator
----------------------------------------------------------------------
laziness is the ultimate motivation of all good system administrators,
any time they can automate, out-source, or otherwise eliminate a task
from their regular routine, it allows them to be more lazy. A truly
lazy system admin would never have to do anything, because everything
would be either automated and done by the machine, or done by users.
The education of users also fulfills this laziness goal, an educated
user will both be more productive, and require less of the admin.
----------------------------------------------------------------------