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]
Other format:	[Raw text]

Re: [RFT/RFA] bashjar patch

From: Paolo Bonzini <bonzini at gnu dot org>
To: gcc-patches at gcc dot gnu dot org
Cc: Andreas Schwab <schwab at suse dot de>, Paolo Bonzini <paolo dot bonzini at lu dot unisi dot ch>, Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Fri, 26 May 2006 14:55:27 +0200
Subject: Re: [RFT/RFA] bashjar patch
References: <e2u1im$niv$1@sea.gmane.org> <20060502192044.GD1691@iam.uni-bonn.de> <4471E06C.6010300@lu.unisi.ch> <jesln1ktfq.fsf@sykes.suse.de> <orhd3d1m0r.fsf@free.oliva.athome.lsd.ic.unicamp.br> <m3ejyhlzwf.fsf@localhost.localdomain>

Andrew H. asks on irc why we don't simply use zip in the build.  Is
there an answer to this?  That may be much simpler.

If we want to provide a decent system to build Java programs, we must provide a jar program to the user. The aim of this patch is first to not break GCJ *for the user*, and only secondarily to allow people to build GCJ without installing a jar program first.

And if we have to provide this jar program, using it to build libjava is just a way to test it, even if only lightly.

Paolo

References:
- Re: [RFT/RFA] bashjar patch
  - From: Ralf Wildenhues
- Re: [RFT/RFA] bashjar patch
  - From: Paolo Bonzini
- Re: [RFT/RFA] bashjar patch
  - From: Andreas Schwab
- Re: [RFT/RFA] bashjar patch
  - From: Alexandre Oliva
- Re: [RFT/RFA] bashjar patch
  - From: Tom Tromey

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