This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
- From: Andrew Haley <aph at redhat dot com>
- To: Angel Tsankov <fn42551 at fmi dot uni-sofia dot bg>
- Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Thu, 30 Oct 2008 11:23:55 +0000
- Subject: Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
- References: <gec1bo$iii$1@ger.gmane.org>
Redirecting to gcc-help.
Angel Tsankov wrote:
> I'm trying to build (natively) GCC 4.3.2 on a
> powerpc-yellowdog-linux-gnu. I have not yet managed to build it all
> ('make bootstrap') but I found out that each of the following changes
> (applied in the order specified) takes me further on:
>
> -- clear the LIBRARY_PATH variable, i.e. build with 'env LIBRARY_PATH=
> make bootstrap';
> -- insert '#include <limits.h>' in libcpp/include/line-map.h:26 (to work
> around errors about undefined CHAR_BIT or UINT_MAX);
> -- insert '#include <limits.h>' in gcc/real.h:29;
> -- add BOOT_CFLAGS='-DENABLE_DECIMAL_FLOAT=1
> -DENABLE_DECIMAL_BID_FORMAT=0' to 'make bootstrap' since these
> macros were not defined (this is stage 2);
> -- insert '#include <limits.h>' in gcc/hard-reg-set.h:24;
> -- insert '#include <limits.h>' in gcc/toplev.h:24;
> -- added -DHAVE_LIMITS_H to BOOT_CFLAGS;
> -- added -DHAVE_GAS_SHF_MERGE=0 to BOOT_CFLAGS;
>
> I wonder if these steps will eventually take me to a successful build of
> GCC. In case this matters, the configuration script identifies the
> build, host, and target systems as powerpc-unknown-linux-gnu.
Something went wrong when you configured gcc.
You should see this in libcpp/config.h:
#define HAVE_LIMITS_H 1
If you don't have this, you need to look at config.log to find out why.
It may be that you need to configure again with a clean tree.
Make very sure that you aren't building in the srcdir.
Andrew.