Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Tue, 13 Jun 2000 19:27:49 -0400 To: Cygwin List Subject: Re: Make and javac compliler problem in bash Message-ID: <20000613192749.H17964@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: Cygwin List References: <4.2.2.20000612160752.00a78a50@gqserver.houston.geoquest.sl <4.2.2.20000613094210.00b3c800@gqserver.houston.geoquest.slb.com> <004601bfd58a$729dca90$f7c723cb@lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <004601bfd58a$729dca90$f7c723cb@lifelesswks>; from robert.collins@itdomain.com.au on Wed, Jun 14, 2000 at 08:55:18AM +1000 On Wed, Jun 14, 2000 at 08:55:18AM +1000, Robert Collins wrote: >Couldn't the existing registry keys used to set per cygwin exe flags be used >to accomplish this, with no?/some? minor changes. I believe they are largely >undocumented but I recall Chris saying something... The flags aren't undocumented. They are the same as the CYGWIN flags, parsed by the same mechanism. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com