On 3/13/12 1:21 PM, Andrew Benton wrote:
> ... and then I tried jhalfs with the vanilla LFS svn book and of
> course, I was wrong again, it failed in exactly the same way! Looking
> at the differences between the book and the scripts that work for me,
> the book has --disable-target-libiberty --disable-target-zlib and my
> scripts have --without-target-libiberty --without-target-zlib (it took
> me a while to see the difference...) If I edit the LFS xml and change
> `disable' to `without' and start again, then it works. It seems that the
> gcc-4.6.3-cross_compile-1.patch does not recognise
> --disable-target-libiberty or --disable-target-zlib
I am completely confused with where we are at here. I want to get to the
bottom as to why the switches are required at all - it shouldn't be a
problem to cross-build zlib or libiberty for x86{,_64}. Can we get back
to comparing notes on builds without the patch and switches?
JH
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
