[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: --with-sysroot conflicts in binutils and gcc
From: |
Ralf Wildenhues |
Subject: |
Re: --with-sysroot conflicts in binutils and gcc |
Date: |
Sat, 23 Oct 2010 09:25:33 +0200 |
User-agent: |
Mutt/1.5.20 (2010-08-04) |
Hello Khem,
* Khem Raj wrote on Thu, Oct 21, 2010 at 10:23:51PM CEST:
> When building gcc and binutils in a cross environment there is a
> conflict with respect to --with-sysroot libtool 2.4 expects
> --with-sysroot on configure options to use sysroot which is fine now
> the build time sysroot and run time sysroot for gcc and binutils might
> differ eg. when building binutils build=x86_64-linux
> host=arm-linux-gnueabi target=arm-linux-gnueabi, in this case we are
> building binutils like a target package in terms of cross compiling
> but if we use --with-sysroot without a value then libtool will guess
> it right pointing to build time sysroot but binutils will then use a
> default sysroot which is not pointing to / on the target file system,
> if we set --with-sysroot="/" then binutils will get it right but
> libtool will get it wrong.
>
> toolchain has two options when it comes to sysroot --with-sysroot and
> --with-build-sysroot I think libtool should also differentiate between
> two and set both to same if not explicitly set during configure time.
> I think libtool means to use build time sysroot and not runtime
> sysroot its just that configure options are colliding
Can we take a step back here. Did you regenerate the GCC and binutils
source trees with Libtool 2.4? Upstream hasn't done that move yet,
precisely because the --with-sysroot issues need to be hashed out first.
Or are you trying to build GCC as well as other sources with the same
configure options?
Thanks,
Ralf