This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

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, 14 Nov 2000 17:20:53 -0500
CC: gcc-patches at gcc dot gnu dot org
References: <20001030214021.A13523@disaster.jaj.com> <200010312011.PAA11075@greed.delorie.com> <20001103205426.A28815@disaster.jaj.com> <200011040233.VAA19588@greed.delorie.com> <20001114171800.C11190@disaster.jaj.com>


> Absolutely.  The general case I had in mind was an n-by-n dependancy
> matrix of "possible things we build" versus "things that they need".
> The Java compiler and libz, the C++ compiler and libstdc++, etc.

All I meant was some generic "extra_target_libs" that's built based on
other config options.  We'd add zlib if java was enabled, libstdc++ if
C++ is enabled, etc.  IIRC, your patch had a $target_zlib variable,
which isn't very generic.

Follow-Ups:
- target library dependancies (was Re: [PATCH] Don't build libzgcj all the time)
  - From: Phil Edwards

References:
- Re: [PATCH] Don't build libzgcj all the time
  - From: Phil Edwards
- Re: [PATCH] Don't build libzgcj all the time
  - From: DJ Delorie
- Re: [PATCH] Don't build libzgcj all the time
  - From: Phil Edwards

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]