gcc goes nuts when you use -c and -o together
Seems the gcc that comes with cooltools goes nuts when you use both -c and -o on a single compilation. For example, with the regular gcc:
$ gcc -v
Reading specs from /usr/sfw/lib/gcc/sparc-sun-solaris2.10/3.4.3/specs
Configured with: /gates/sfw10/builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared
Thread model: posix
gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
$ gcc test.c -c -o test.foo
(no output, test.foo is created)
but with cooltools:
$ gcc -v
Using built-in specs.
Target: sparc-sun-solaris2.10
Configured with: /export/home/bldmstr/nightly/20060207_gcc2ir.s10.opt.tarbuild/src/configure --prefix=/opt/gcc --enable-languages=c,c++
Thread model: posix
gcc version 4.0.2 (gccfss)
$ gcc test.c -c -o test.foo
.section".text",#alloc,#execinstr,#progbits
.file"test.c"
... (more garbage follows, test.foo not created)
DS
