[build] Move unwinder to toplevel libgcc (v2)
Joseph S. Myers
joseph@codesourcery.com
Thu Aug 11 14:44:00 GMT 2011
On Thu, 11 Aug 2011, Paolo Bonzini wrote:
> On 08/11/2011 04:25 PM, Joseph S. Myers wrote:
> > > The actual problem are not the runtime libraries, which already know to
> > > search $builddir/.../libgcc for unwind.h and related files. The
> > > copyback is only for the benefit of the testsuite (gcc.target, g++.dg,
> > > gnat.dg, and gcc.dg) where I was too lazy to deal with changing (or even
> > > setting ) the include paths, but took the easy way out since gcc/include
> > > is in the include path by default.
> >
> > unwind.h is an installed header. Are you sure nothing outside of GCC uses
> > it?
>
> Why does it matter? It is still installed in trunk, and you could also move
> the installation to libgcc's Makefiles if it weren't copied anymore to
> $builddir/gcc/include.
Actually I think the installation of all the installed target headers
should move to libgcc's Makefiles (and the headers themselves should move
under the libgcc/ directory).
--
Joseph S. Myers
joseph@codesourcery.com
More information about the Libstdc++
mailing list