Hi,
This is what I did:
I. Unpacked sources
1. # mkdir /opt/gcc-4.3.2
2. Under /opt/gcc-4.3.2, I unpacked the gcc sources
3. Both gmp, mpfr. And binutils are unpacked under /opt/gcc-4.3.2
II. Build and configure
* build and configure binutils under
/opt/build_binutils using /usr/local/gcc-4.3.2 as prefix
* build and configure gmp and mpfr in their
directory /opt/gcc-4.3.2/gmp and
/opt/gcc-4.3.2/mpfr using /usr/local/gcc-4.3.2 as prefix
III. GCC-4.3.2
* Configure and build in /usr/local/gcc-4.3.2 as follows
* # cd /usr/local/gcc-4.3.2
* /usr/local/gcc-4.3.2 #
/opt/gcc-4.3.2/configure ?prefix=/usr/local/gcc-4.3.2 etc
4. /usr/local/gcc-4.3.2 # make --- this went it failed
My understanding:
The prerequisites for GCC indicate that both gmp
and mpfr will be built together with GCC if they
are subdirectories of the GCC sources. I tried
that but had problems since gcc did not know
where to get gmp.h amd mpfr.h and their
libraries. However, when I configured and
compiled both of them it their source directories
using /usr/local/gcc-4.3.2 as prefix, I did not
have that problem. Both gmp and mpfr have
information about how to configure and build
which do not seem to be in parallel with the gcc
instllation found on
<http://gcc.gnu.org/install/>http://gcc.gnu.org/install/.
I do not think a really understand about building
gmp and mpfr together with gcc.
Please further advise me of what I am doing wrong.
Thanks to all
X-Originating-IP: [195.156.147.13]
Date: Mon, 26 Jan 2009 14:05:15 +0200
From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
To: Franklyn Simon <franklynsimon@xxxxxxxxxxxxx>
Subject: Re: GCC-4-3.2 Build /Possible configuration problems
Franklyn Simon wrote:
Here is the attached config.log file and output from make -j1
It appears that configuration was okay, but I cannot get to build.
After looking at the config.log file its
indicates the following two possible errors. I
do not know how to go about solving then
Please help. I am using gcc-g++3.3.3 compiler
and SLES9 on hp pavilion a305w (i686-pc). I am going a native build
Your log tells that you aren't trying to build "only gcc-4.3.2" but to
try some kind of "everything at the same time" : binutils, gmp, GCC,...
and your build crashing during the 'gmp' build...
Traditionally these things have been splitted into smaller pieces so the
GNU binutils, the GCC, the 'gmp' etc. sources are 'stand-alone' with
their own 'bfd', 'libiberty' etc. subdirs. But there can be those
"combined GNU sources" like those GNUpro ones from Red Hat and in them
builds like yours should work. But in them many people have worked in
order to get things to work together.
Ok, something is wrong in your 'gmp' source install :
----------- clip -------------
make[3]: Leaving directory `/usr/local/gcc-4.3.2/binutils'
Configuring stage 1 in ./gmp
configure: loading cache ./config.cache
checking build system type... i686-pc-linux-gnu
checking host system type... none-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
make[2]: Leaving directory `/usr/local/gcc-4.3.2'
make[1]: Leaving directory `/usr/local/gcc-4.3.2'
configure: error: source directory already configured; run "make
distclean" there first
make[2]: *** [configure-stage1-gmp] Error 1
----------- clip -------------
The GCC's "Prerequisites" say that the 'gmp-*' and 'mpfr-*' sources
could be installed as 'gmp' and 'mpfr' subdirs into the GCC sources.
Did you really do this? Not for instance installing them being
"parallel with the GCC sources" ?
Building binutils then happens "parallel", totally separately from
the GCC sources so one can have '$src/gcc-4.3.2' and
'$src/binutils-2.19' but '$src/gcc-4.3.2/gmp' and '$src/gcc-4.3.2/mpfr'
for the 'gmp-*' and 'mpfr-*' sources...
The $build directory should be a separate one from the sources...
Where are your GCC sources? They MUST NOT be in '/usr/local' ! Using
that as your chosen '$build' directory sounds really weird. Something
like :
/usr/local/src
for the unpacked srcs like '/usr/local/src/gcc-4.3.2',
'/usr/local/src/gmp-4.2.1', '/usr/local/src/mpfr-2.3.2' etc. would
be more "normal". After unpacking the srcs there a suitable $build
directory could be the :
/usr/local/build
and configuring & building there... Just as the "Install" Prerequisites
are telling, one could then have in '/usr/local/src/gcc-4.3.2' :
gmp -> ../gmp-4.2.1
mpfr -> ../mpfr-2.3.2
and both 'gmp' and 'mpfr' being built during the GCC build....
The '/usr/local' is quite like '/usr' in a Linux system, aimed for
local-made apps ('bin'), libraries ('lib'), headers ('include') etc.
Anything might happen if one thinks that it is not used for anything
in the system... I myself use '/home/src' as the install place for
all kind of source distributions...
I tried the "build 'gmp' and 'mpfr' during the gcc-4.3.2 build and
things seemed to work even in a $build != $host case (cross-compiling
also 'gmp' and 'mpfr' for the '$host' platform while producing GCC
binaries for that...
