Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu

2008-10-30 Thread Angel Tsankov 
Hi,

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.

Thanks in advance,
Angel Tsankov

Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu

2008-10-30 Thread Ben Elliston 
 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 [EMAIL PROTECTED]

Thanks, Ben

-- 
Ben Elliston [EMAIL PROTECTED]
Australia Development Lab, IBM