This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Java and zlib
- To: gcc at gcc dot gnu dot org, Anthony Green <green at redhat dot com>
- Subject: Java and zlib
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Tue, 19 Sep 2000 16:11:19 +0200 (CEST)
Due to the following change
2000-09-02 Anthony Green <green@redhat.com>
* jcf-io.c: Include zlib.h.
(open_in_zip): Read compressed class file archives.
GCC fails to build on several of my "minimal" boxes:
../stage1/xgcc -B../stage1/ -B/sw/test/gcc/SunOS/sparc-sun-solaris2.6/bin/ -c -DIN_GCC -DSVR4 -O2 -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wno-long-long -W -Wall -I. -I.. -I/sw/test/gcc/gcc/gcc/java -I/sw/test/gcc/gcc/gcc/java/.. -I/sw/test/gcc/gcc/gcc/java/../config -I/sw/test/gcc/gcc/gcc/java/../../include -I/sw/test/gcc/gcc/gcc/java/../../zlib /sw/test/gcc/gcc/gcc/java/jcf-io.c
/sw/test/gcc/gcc/gcc/java/jcf-io.c:33:18: zlib.h: No such file or directory
I am aware that there has been a bit of discussion on whether to include
zlib in the tree, but I believe that the current situation is definitely
undesirable.
Problem #1: zlib as a required package is not mentioned anywhere in
our install documentation.
Problem #2: If this is a required package, its existence should be
verified at configure time, instead of aborting the bootstrap after
it's already half through.
(Or should zlib be checked for during configure and only be used if
it is present? If so, still the documentation needs to mention that.)
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/