> >If you configure gnustep-make by using
> >
> >CC=gcc3 ./configure
> >
> >then gnustep-make will set the default compiler to be used for gnustep to
> >gcc3. Whenever you compile anything related to gnustep, gnustep-make will
> >automatically use gcc3 to compile.
> >
> >When you configure the other gnustep packages, do
> >
> >CC=gcc3 ./configure
> >
> >in the same way, because they might be checking for compiler options (the
> >base library in particular).
>
>
> To use a different compiler for a particular run of make, you can also use:
>
> CC=gccXXX make target
Yes - exactly - but this is for power users who like risky adventures only
:-) because it would not normally work - because of the complex changes
which were done in the recent gcc compilers. If you switch the compiler
for a single run of make, you must make sure that it's `compatible' with
the default compiler for gnustep ... since stuff like thread flags or
constant string flags or other compiler options might be stored in the
config ... other objc libraries might have been compiled using that
options making on-the-fly switch of compiler even more difficult ... you
might be able to tweak all flags and problems and to use a different
compiler for a single run (still depending on the exact compilers) ... but
obviously if you do that, you're on your own risky adventure.
The default recommendation for everyone to get safely a working system
with multiple compilers is to choose one which works with gnustep, and
./configure all packages using CC=myCompiler ./configure, and never try to
mix code compiled by different compiler versions.
But if you ever need to do that, David is right, you can ask gnustep-make
to do it.