RE: libstdc++ ignores --with-sysroot? [was: crosstool-0.28-rc13+ arm9 softfloat, sysroot success]

["Ruhland, Paul" <PRuhland at microwavedata dot com>]

Looking at the GCC Docs, '--with-sysroot' only specifies where it looks for
headers and libraries not where it puts its headers and libraries.  So it
seems its working as documented.

The crosstool glibc library install in '$PREFIX/$TARGET/sys-root' is done
via the 'install_root' arg to make install.

It would be convienent from a target perspective to have all the libraries
and includes in 'sys-root' as that directory becomes a nice root filesystem
basis for the target.  Would it be possible to control where gcc puts its
libraries and includes via the '--with-gxx-include-dir' and '--with-slibdir'
directives?  I've typically never had success fiddling with these...mayhap
I'll try again.

-----Original Message-----
From: Ralf Corsepius [mailto:corsepiu@faw.uni-ulm.de]
Sent: Thursday, May 27, 2004 7:32 AM
To: Dan Kegel
Cc: Dimitry Andric; Ruhland, Paul; crossgcc@sources.redhat.com;
libstdc++@gcc.gnu.org
Subject: Re: libstdc++ ignores --with-sysroot? [was:
crosstool-0.28-rc13+ arm9 softfloat, sysroot success]


On Wed, 2004-05-26 at 17:16, Dan Kegel wrote:
> Dimitry Andric wrote:
> > On 2004-05-26 at 16:26:58 Ruhland, Paul wrote:
> > 
> >>I built [gcc] using the 'sys-root' config option.  This works great and
leaves
> >>you with a great target filesystem skeleton (include libraries, headers,
> >>etc) in the 'sys-root' directory.
> > 
> > 
> >>One small issue with the 'libstdc++' libs not being put in
> >>'sys-root/usr/lib'.  Not a big deal if just using C.
> > 
> > 
> > Yes, these end up in $PREFIX/arm-linux/lib instead of (as I expected)
> > $PREFIX/arm-linux/sys-root/usr/lib, just like libgcc_s, libsupc++ and
> > libiberty.  I have no idea why.  Does anyone on the list know the
> > rationale behind this?
> 
> Nope.  I bet the libstdc++ developers just haven't cottoned on to
> gcc's --with-sysroot configure option yet.
IMO, gcc's / libstdc++'s behavior is correct, because it treats
sys-root as read-only directory and puts all generated files (headers,
libs etc.) into its private directories.
libstdc++ and its headers are such private files.

Ralf



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com