Re: configure --with-sysroot

[<gp at qnx dot com>]

This would be ideal.  I'm not sure I can sell the symlink idea, though.  One
of the things we try to avoid is duplication of installed files, and on
Windows hosts, we cannot guarantee that the user will have a filesystem that
supports soft links, so we end up with potentially 8 installed copies of the
entire common system include tree - one copy for each target CPU variant.

I'd love to spec/multilib the sysroot _and_ allow the header_sysroot to be
separately specified at configure and/or via specs.

I have attached my first run at the --with-header-sysroot changes.  I took the
approach of having --with-sysroot set the sysroot and the header_sysroot, and
then if --with-sysroot is specified, it only overrides the header_sysroot stuff.

Regardless of whether this looks ok or not, any pointers on how one would go
about implementing spec'ed sysroot/header_sysroot?

Thanks.
GP

Alexandre Oliva <aoliva at redhat dot com> said:

> On Mar  5, 2003, <gp at qnx dot com> wrote:
> 
> >   --with-headers-sysroot sets only TARGET_HEADER_SYSTEM_ROOT
> >   --with-library-sysroot sets only TARGET_BINARY_SYSTEM_ROOT
> >   --with-sysroot sets them both and takes priority.
> 
> > Does that sound ok?  Any gotchas I should be aware of? 
> 
> I'd much rather have `spec'ed sysroots, i.e., something that,
> depending on the multilib in effect, chooses a different sysroot.
> You can always share the headers by means of soft links, and the
> advantage is that each sysroot is a real sysroot.
> 
> -- 
> Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer                 aoliva at {redhat dot com, gcc.gnu.org}
> CS PhD student at IC-Unicamp        oliva at {lsd dot ic dot unicamp dot br, gnu.org}
> Free Software Evangelist                Professional serial bug killer
> 



--

Attachment: header_sysroot.diff
Description: Binary data