building gcc 4.0.0 on Solaris

Dimitri Papadopoulos-Orfanos papadopo@shfj.cea.fr
Tue May 10 11:57:00 GMT 2005


Hi,

> How did you configure?  The mix of GNU tools and Sun tools looks suspicious.

I think there's no mix involved.

I have configured with:
	./configure \
		--with-as=/usr/local/binutils/bin/as \
		--with-ld=/usr/local/binutils/bin/ld \
		...
so I should be using GNU's as and ld.

> libgcj.so.6.0.0 is a monster so that could be a memory problem too.  If you're 
> not interested in Java, I'd suggest to configure with --disable-libgcj.

Yes, I do have a first version built with --enable-languages=c,c++ only, 
but I'd like to have a complete version.

Otherwise it's not a memory problem, I have enough memory:
	$ top
	...
	Memory: 1024M real, 243M free, 2457M swap in use, 225M swap free
	...

>>Has anyone attempted to use GNU binutils 2.16 to build gcc on 
>>Solaris?
> 
> 
> I have (with a 2.16 prerelease) on Solaris 2.5.1, 2.6, 7, 8 and 9.  I'll try 
> with the stock release.
> 
> 
>>In any case it looks like gcc cannot be built on Solaris using standard
>>GNU binutils releases.
> 
> 
> 2.15 is the only one problematic, unless proven otherwise.

No, I've had problems with almsot all other previous GNU binutils 
releases, see my previous posts on this list. Maybe GNU binutils 2.13 or 
2.14 did work at some point.

--
Dimitri



More information about the Gcc mailing list