the new build system in binutils sets up custom LD_LIBRARY_PATHs which can cause
conflicts between the build and host. if you take binutils-2.17.50.0.17 and
build/install it with --enable-shared, your host binutils will all be linked
against libbfd-2.17.50.0.17.20070615.so:
$ readelf -d `which as
--- Additional Comments From nickc at redhat dot com 2007-08-28 12:06
---
Subject: Re: windres does not escape path with spaces
in them
Hi Manu,
> Do you have some information on how I can get the CVS binutils
See:
http://www.gnu.org/software/binutils/binutils.html
> and compile i
Hi Manu,
Do you have some information on how I can get the CVS binutils
See:
http://www.gnu.org/software/binutils/binutils.html
and compile it on Windows?
See the README file at the top level in the sources you checked out of the CVS
repository. Assuming that you are using a Cygwin or Mi
--- Additional Comments From schwab at suse dot de 2007-08-28 08:49 ---
You did not configure glibc correctly. You should use --prefix=/usr and
install it with install_root=${sysroot}. The whole point of the sysroot
feature is that it establishes a chroot style environment.
--
While trying to compile gcc (HEAD of 2007-08-27) for a sysrooted environment in
/tmp/gc where glibc 2.6.1 is already installed there, ld complains:
/usr/i686-pc-linux-gnulibc2/lib/gcc-lib/i686-pc-linux-gnulibc2/3.3.3/../../../../i686-pc-linux-gnulibc2/bin/ld:
cannot find /tmp/gc/lib/libc.so.6 insid
