Gale Paeper wrote:
Maybe putting CC= ... in front of 'configure' does the job also.
Since your Mac OS X build-on script command files are set up to run in a tcsh shell, you need to use the command form of:
setenv CC /Developer/Pascal/gpc412d1/bin/gcc
With that command just before the cross compiler configure command, the /Developer/Pascal/gpc412d1/bin/gcc compiler is always used in building the cross compiler and the build succeeds without error.
I'm not familiar with how a tcsh shell handles environment variables set in a shell command file so I'm not sure how benign that command actually is in a global, system wide context. As far as I can tell, the effect of setting of CC seems to go away when the tcsh shell process executing the shell command file terminates.
I note the gcc configuration documentation, http://gcc.gnu.org/install/configure.html, states "setting cc in your environment" is one way to specify the c compiler to be used for compiling so it is probably the way to go to workaround the present PowerPC hosted cross compiler build error problem.
Yes, that seems to be the best way to work around the build/apple-gcc problem.
Regards,
Adriaan van Os