Re: gcc problem

[Riccardo Mottola]

Hi,
> > > checking whether the C compiler works... configure: error: cannot 
> > > run C compiled programs.
> >
> > This one is familiar.  I had this problem while trying to compile GCC 
> > in /tmp on a cluster.  The partition was mounted with the noexecute 
> > flag.  You need to make sure that you are building GCC somewhere 
> > where it can emit binary files that they can run.  The cross-compile 
> > line is a red herring; one common cause for this problem is if you 
> > are building a cross compiler the host probably won't be able to run 
> > binaries compiled for the target system.
>
> I am building gcc in /usr/src as root and it can do there whatever it 
> wants!? I don't wantto build a cross-compiler. Is this the default? 
> How can I switch that off in the ../configure line:
>
>     ../configure --with-gnu-as --with-as=/usr/sfw/bin/gas 
> --without-gnu-ld --with-ld=/usr/ccs/bin/ld --enable-shared 
> --disable-nls --enable-languages=c,c++,objc
I used to do quite some gcc compiles to have gcc on some of my 
less-mainstream platforms.

It is painful. And every gcc past 3.2 has become a pain in the ass. 4.1 
was the last one which I got to at least build up to the end on most of 
my computer. The newest ones are very terrible.

I remember when the gcj guy used to compile and test on my SMP-sparc32 :)

anyway, using non gnu linkers and assemblers is usually a lost battle. 
Especially mixing them, like you are trying to do.
The unfortunate thing is that gnu as and ld are not always the best on 
the platform of choice...

Also, which compiler are you using to bootstrap? latest gcc 4.x series 
work only with gcc 3.2 and newer.

Check on the sun freeware site, there are the configure options for 
their packages.

Just give it a try with the gnu linker.

Riccardo