public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Java and zlib
@ 2000-09-19  7:11 Gerald Pfeifer
  2000-09-19  7:32 ` Daniel Berlin
  2000-09-19  7:45 ` Franz Sirl
  0 siblings, 2 replies; 5+ messages in thread
From: Gerald Pfeifer @ 2000-09-19  7:11 UTC (permalink / raw)
  To: gcc, Anthony Green

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/

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Java and zlib
  2000-09-19  7:11 Java and zlib Gerald Pfeifer
@ 2000-09-19  7:32 ` Daniel Berlin
  2000-09-19  7:41   ` Gerald Pfeifer
  2000-09-19  7:45 ` Franz Sirl
  1 sibling, 1 reply; 5+ messages in thread
From: Daniel Berlin @ 2000-09-19  7:32 UTC (permalink / raw)
  To: Gerald Pfeifer; +Cc: gcc, Anthony Green

Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:


Err, zlib is in the GCC tree now.
Your update must not have caught it.

cvs -z4 -q update -dP zlib in the root of your gcc cvs tree ought to
make it appear.
> (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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Java and zlib
  2000-09-19  7:32 ` Daniel Berlin
@ 2000-09-19  7:41   ` Gerald Pfeifer
  2000-09-19 10:25     ` Richard Henderson
  0 siblings, 1 reply; 5+ messages in thread
From: Gerald Pfeifer @ 2000-09-19  7:41 UTC (permalink / raw)
  To: Daniel Berlin; +Cc: gcc, Anthony Green

On 19 Sep 2000, Daniel Berlin wrote:
> Err, zlib is in the GCC tree now.
> Your update must not have caught it.

<ouch> 

My bad. I'm completely embarrassed!

Sorry,
Gerald

PS: Perhaps we could have configure abort if it does not find zlib.h?
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Java and zlib
  2000-09-19  7:11 Java and zlib Gerald Pfeifer
  2000-09-19  7:32 ` Daniel Berlin
@ 2000-09-19  7:45 ` Franz Sirl
  1 sibling, 0 replies; 5+ messages in thread
From: Franz Sirl @ 2000-09-19  7:45 UTC (permalink / raw)
  To: Gerald Pfeifer; +Cc: gcc, Anthony Green

At 16:11 19.09.00, Gerald Pfeifer wrote:
>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.)

Maybe you forgot to run ./contrib/gcc_update with the -dP option? zlib _is_ 
part of the tree now and lives in the toplevel.

Franz.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Java and zlib
  2000-09-19  7:41   ` Gerald Pfeifer
@ 2000-09-19 10:25     ` Richard Henderson
  0 siblings, 0 replies; 5+ messages in thread
From: Richard Henderson @ 2000-09-19 10:25 UTC (permalink / raw)
  To: Gerald Pfeifer; +Cc: Daniel Berlin, gcc, Anthony Green

On Tue, Sep 19, 2000 at 04:41:07PM +0200, Gerald Pfeifer wrote:
> PS: Perhaps we could have configure abort if it does not find zlib.h?

*shrug*  I don't see that that's any different from
the compilation error that you got.


r~

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2000-09-19 10:25 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-09-19  7:11 Java and zlib Gerald Pfeifer
2000-09-19  7:32 ` Daniel Berlin
2000-09-19  7:41   ` Gerald Pfeifer
2000-09-19 10:25     ` Richard Henderson
2000-09-19  7:45 ` Franz Sirl

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).