[Bug bootstrap/35752] [4.3/4.4 Regression]: Combined gcc + binutils source tree doesn't bootstrap with --enable-shared

[Ralf dot Wildenhues at gmx dot de]

------- Comment #54 from Ralf dot Wildenhues at gmx dot de  2008-04-22 05:27 -------
Subject: Re:  [4.3/4.4 Regression]: Combined gcc +
        binutils source tree doesn't bootstrap with --enable-shared

* bonzini at gnu dot org wrote on Mon, Apr 21, 2008 at 04:39:20PM CEST:
> For win32 it suffices to:
> 
> 1) create wrapper executable under random name
> 2) create wrapper script under random name
> 3) move wrapper script to correct name
> 4) move wrapper executable to correct name

Probably.  Libtool 2.2.2 has things changed there, and a couple of
issues still, so I need to look at this anyway.

> (BTW, were you libtool maintainers aware of this race/these races?)

I wasn't.  But I don't think we guarantee atomic creation of output.
Take the trivial case: program needs no relink.  In that case, it's
up to the compiler/linker whether the program is created atomically.
GCC doesn't do it.  :-)

So I'm not yet convinced this particular race to be a Libtool bug.

> The problem is that you want to make a combined tree with released gcc 
> and binutils, and since this is arguably a gcc bug you want the latest 
> gcc without the bug to compile a combined tree with any released 
> binutils version.

Ah ok.

> At worse, we could just pass --disable-fast-install in the toplevel 
> configure when gcc is present.  That could be a solution for 4.3 actually.

But then you may not strictly install ld-new, as it may not work on some
systems.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35752