On Wed, 14 Mar 2012 22:05:37 +0000
Pierre Labastie <pierre.labas...@neuf.fr> wrote:
> I have libgfortran, libgo, libffi, libjava, libobjc in the source dir!
> Could it be that
> since you do not have those dirs, configure somehow "forgets" to
> disable target-zlib? Have you tried to build
> with the full source of gcc?
Thank you! That's it. That's what I'm doing differently. I just
download gcc-core and gcc-g++. For jhalfs I untared them and then tared
them again into a gcc-4.6.3 tarball so it had the right name. When I
started doing LFS we used to just download the gcc-core and gcc-g++
tarballs and I've just kept doing it that way. I've been doing it for
so long it never occurred to me that it might cause a problem.
With the full gcc-4.6.3 tarball I get the same results as everybody
else, configure says:
*** This configuration is not supported in the following subdirectories:
target-libquadmath gnattools target-libada target-libstdc++-v3
target-libgfortran target-libgo target-libffi target-zlib target-libjava
target-libobjc target-libgomp target-libmudflap target-libssp target-boehm-gc
(Any other directories should still work fine.)
(complete with target-zlib listed there) and make succeeds. So at last
the mystery is solved. The gcc cross patch is needed if you haven't
downloaded the full gcc tarball. The book is still wrong by the way, it
still has --disable-target-zlib, which the patch doesn't recognise (it
silently ignores those options), the patch recognises
--without-target-zlib or --with-target-zlib=no. rm -rf zlib works too.
Andy
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
