This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
- From: Ben Elliston <bje at au1 dot ibm dot com>
- To: Angel Tsankov <fn42551 at fmi dot uni-sofia dot bg>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 31 Oct 2008 09:47:09 +1100
- Subject: Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
- References: <gec1bo$iii$1@ger.gmane.org>
> 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:
>
> -- 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;
You should not have to make any of these changes to bootstrap GCC 4.3.2
on a PowerPC GNU/Linux system. We build these compilers regularly and
do not have to do this.
I think you're probably building GCC incorrectly. Please follow-up with
a list of your steps to gcc-help@gcc.gnu.org.
Thanks, Ben
--
Ben Elliston <bje@au.ibm.com>
Australia Development Lab, IBM