This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Don't build libzgcj all the time
- To: pedwards at disaster dot jaj dot com
- Subject: Re: [PATCH] Don't build libzgcj all the time
- From: DJ Delorie <dj at redhat dot com>
- Date: Tue, 31 Oct 2000 15:11:32 -0500
- CC: gcc-patches at gcc dot gnu dot org
- References: <20001030214021.A13523@disaster.jaj.com>
> Building libzgcj is pointless unless Java is one of the enabled languages.
Is it any more or less pointless than any other generic target
library? I'm not against this patch, but what happens in the future
when some other project which shares the toplevel configure.in decides
it wants libz for its target, and has to compete with java-specific
conditionals?
Normally, target libraries are excluded from a build for one of
two reasons:
1. The sources don't exist. If cvs doesn't get them, configure won't
build them. Perhaps a new cvs module for java-less gcc?
2. The can't be compiled for the given target.
Plus, there already exists a mechanism for skipping target libraries -
$noconfigdirs. It does, however, print "This configuration is not
supported in . . . target-zlib". Have you reviewed that mechanism to
see if it can be used?