GCC 3.2.3 on Solaris 2.7

Balaji Srinivasa Balaji@bladelogic.com
Mon Mar 22 17:04:00 GMT 2004


> 
> > 4. I built Python 2.1 for a 32 bit sample
> > 5. I built lsof 4.70 for a 64 bit sample
> > 6. They both built successfully and ran successfully.
> 
> Nice!
> 
> > I am thinking that these failures might be due to
> > (a) me setting --disable-libgcj
> > (b) me setting --enable-languages=c,c++,objc
> > and the building of the sparcv9 dirs.
> 
> No, I don't think so, these are common and well-tested 
> options.  I'd tend to 
> think of a shell problem if you used /bin/sh, such problems are very 
> frequent on Solaris.
> 
> > This did not happen on 2 other 32 bit builds.
> > 1. Solaris 2.6
> > 2. Linux 2.4
> 
> Sure, sparc-sun-solaris2.6 is not multilibed.
I think the shell was the problem. In fact, the documentation
should state that CONFIG_SHELL should always be exported, or,
configure should take the SHELL value from the env.

After that was set, a complete rebuild was successful.

However, config.status still shows #!/bin/sh whatever is set.

thx to Eric,
balaji



More information about the Gcc mailing list