compiling propgcc on osx (10.4, no 64-bit capabilities)
softcon
Posts: 217
Since the only binaries for propgcc are posted for 64-bit systems, I was going to attempt to compile my own version of propgcc. I did download the code when it was in alpha, but don't remember if I did anything with it or not.
So, fresh download today, and then started the rebuild.sh script.
(it was a strong temptation to build it all manually, since that's my nature, and instructions were provided, but I figured let the automatic process have it's chance first)
So, during the binutils process, it came up with this error.
Anyone here have a quick solution for this one? I've never had much luck fixing gcc compile errors when it's a big project like this one. automake and friends is beyond me. I like small projects, where I can modify the code directly when something happens.
I'm sure this one has a (relatively) simple solution, assuming of course, gcc 4.0.1 can actually do the compile. Any help would be appreciated.
So, fresh download today, and then started the rebuild.sh script.
(it was a strong temptation to build it all manually, since that's my nature, and instructions were provided, but I figured let the automatic process have it's chance first)
So, during the binutils process, it came up with this error.
gcc -DHAVE_CONFIG_H -I. -I../../../propgcc/binutils/ld -I. -I../../../propgcc/binutils/ld -I../bfd -I../../../propgcc/binutils/ld/../bfd -I../../../propgcc/binutils/ld/../include -g -O2 -DENABLE_PLUGINS -DLOCALEDIR="\"/opt/parallax/share/locale\"" -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 -MT ldlang.o -MD -MP -MF .deps/ldlang.Tpo -c -o ldlang.o ../../../propgcc/binutils/ld/ldlang.c cc1: warnings being treated as errors In file included from ../../../propgcc/binutils/ld/ldlang.c:43: ../../../propgcc/binutils/ld/../bfd/libbfd.h:2283: warning: declaration of 'link_info' shadows a global declaration ../../../propgcc/binutils/ld/ldmain.h:42: warning: shadowed declaration is here make[4]: *** [ldlang.o] Error 1Now, since I'm running 10.4 tiger, I don't exactly have the latest compilers, but I am using gcc 4.0.1.
Anyone here have a quick solution for this one? I've never had much luck fixing gcc compile errors when it's a big project like this one. automake and friends is beyond me. I like small projects, where I can modify the code directly when something happens.
I'm sure this one has a (relatively) simple solution, assuming of course, gcc 4.0.1 can actually do the compile. Any help would be appreciated.
Comments
Hi.
It's unclear at this point what the best path is. You may have hit a bug in the native gcc 4.0.1 compiler. Updating the native gcc compiler would be best if possible.
If one could turn off -Werror by using NO_WERROR in the makefiles, the compile might get further along, but another warning may appear later.