[build] Move unwinder to toplevel libgcc (v2)

Paolo Bonzini bonzini@gnu.org
Wed Aug 10 15:59:00 GMT 2011

On 08/10/2011 03:56 PM, Rainer Orth wrote:
> "Joseph S. Myers"<joseph@codesourcery.com>  writes:
>>> This is strange: they copy explicitly goes into $(gcc_objdir): from
>>> libgcc/Makefile.in:
>>> install-unwind_h:
>>>          cp unwind.h $(gcc_objdir)/include/unwind.h
>>>          chmod a+r $(gcc_objdir)/include/unwind.h
>>> For an in-tree build, the source directory cannot be read-only, for a
>>> VPATH build I don't see how this can happen.  Could you please check?
>> This is a VPATH build and the issue is that the *file* unwind.h is
>> readonly having been copied from a readonly source (and install-unwind_h
> I see.  I'd been thinking of a source tree mounted read-only, not the
> actual files changed to be read-only.
>> must, I suppose, end up getting called more than once so that the second
>> copy tries to copy over a readonly file; the 26478 fix was to remove the
> True: it is called once per multilib.

Just to doublecheck, are we sure that unwind.h is always the same?


More information about the Libstdc++ mailing list