This is the mail archive of the mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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.


Want more information?  See the CrossGCC FAQ,
Want to unsubscribe? Send a note to

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]