This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

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

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

From: Dan Kegel <dank at kegel dot com>
To: Dimitry Andric <dimitry at andric dot com>
Cc: "Ruhland, Paul" <PRuhland at microwavedata dot com>, crossgcc at sources dot redhat dot com, libstdc++ at gcc dot gnu dot org
Date: Wed, 26 May 2004 08:16:12 -0700
Subject: libstdc++ ignores --with-sysroot? [was: crosstool-0.28-rc13+ arm9softfloat, sysroot success]
References: <76C7EB7C8500594F9001B118E7E778F48F4DDD@mdsms3.inside.mdsroc.com> <564731114.20040526171108@andric.com>

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.
- Dan

--
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change

Follow-Ups:
- Re: libstdc++ ignores --with-sysroot? [was: crosstool-0.28-rc13+arm9 softfloat, sysroot success]
  - From: Benjamin Kosnik

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