delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/05/18/08:35:29

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 18 May 2005 13:19:40 +0100 (BST)
From: jules <jules AT acris DOT dsvr DOT co DOT uk>
To: "Gerrit P. Haase" <gerrit AT familiehaase DOT de>
cc: cygwin AT cygwin DOT com
Subject: Re: dllwrap command line processing problem
In-Reply-To: <428B2CFB.5060209@familiehaase.de>
Message-ID: <Pine.LNX.4.44.0505181318480.23184-100000@acris.dsvr.co.uk>
MIME-Version: 1.0

Well, sure that's possible.  And I'm able to work around the problem here 
easily enough... I just think if dllwrap is distributed, it ought to be 
correctly documented and not silently ignore command line options.

Jules

On Wed, 18 May 2005, Gerrit P. Haase wrote:

> jules wrote:
> 
> > I'm using a rather outdated version, so I'm not sure if this has been 
> > fixed, but dllwrap seems to ignore the "--mno-cygwin" command line option 
> > that is documented in its --help output.  "-mno-cygwin" works as expected.
> > 
> > $ dllwrap --version
> > GNU dllwrap 2.15.91 20040725
> > Copyright 2004 Free Software Foundation, Inc.
> 
> Why not use gcc as driver?
> 
> 
> Gerrit
> -- 
> =^..^=
> 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019