Request for Assistance: GCC 3.3.1 Code-Gen Problems

[Phil Edwards]

On Tue, Jul 15, 2003 at 11:47:02PM +0200, Eric Botcazou wrote:
> > So, if we use whatever procedure is documented in install.texi, things
> > work OK?  It's only that Phil's trying to set CONFIG_SHELL that messes
> > things up?
> 
> No, setting CONFIG_SHELL is strongly recommended, otherwise we get bootstrap 
> failures with libstdc++ and libjava on Solaris 8 and earlier

Yep.

I think even setting CONFIG_SHELL to /bin/sh would cause the same problems,
although I won't be able to test that hypothesis until tomorrow.  After
setting CONFIG_SHELL, the expansion of the INSTALL* variables contains an
extra word, which then appears to confuse libtool during installation:  it
sees

    /bin/whateversh ...../install-sh -args file-to-install directory

and seems to end up in an off-by-one situation, thinking that file-to-install
is the target installation directory.


> (Solaris 9' sh 
> seems to be more cooperative in this matter).

Interesting.  Sun had pledged not to make any incompatible changes in the
traditional /bin/sh.  This is good news.


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams