Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
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 ' in libcpp/include/line-map.h:26 (to work
around errors about undefined CHAR_BIT or UINT_MAX);
-- insert '#include ' 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 ' in gcc/hard-reg-set.h:24;
-- insert '#include ' 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: GCC 4.3.2 ignores -I. if used with other -I directives?!
Angel Tsankov wrote: > Result on my system: > dbgcnt.o: ../dbgcnt.c ../include/config.h > I meant that on my system the commands produce exactly the same result, i.e. the -I. option seems to be ignored.
Re: GCC 4.3.2 ignores -I. if used with other -I directives?!
Angel Tsankov wrote: > [..] the -I. option seems to be ignored. A further investigation reveals that GCC ignore not only "-I." but also "-I".
GCC 4.3.2 ignores -I. if used with other -I directives?!
Hi, Here's how the test case: 1. Create the following directory tree: |--include/config.h (may be empty) |--source/config.h (may be empty) \--dbgcnt.c (contains only '#include "config.h"') 2. Go to directory "source" and execute the following commands: gcc -M -I../include -I. ../dbgcnt.c gcc -M -I. -I../include ../dbgcnt.c Result on my system: dbgcnt.o: ../dbgcnt.c ../include/config.h Is this the expected result or smth is wrong? Regards, Angel Tsankov
Re: GCC 4.3.2 ignores -I. if used with other -I directives?!
Angel Tsankov wrote: > Angel Tsankov wrote: >> [..] the -I. option seems to be ignored. > > A further investigation reveals that GCC ignore not only "-I." but > also "-I". > Still further investigation shows that versions 2.95.4, 3.0.4, and 3.1.1 take into account "-I", while versions 3.2.3 and 4.3.2 ignore such options. Any ideas why? Angel
