Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Mon, 19 May 2003 17:22:18 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: David Abrahams <dave AT boost-consulting DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: Strange Cygwin issue
In-Reply-To: <ullx3l48a.fsf@boost-consulting.com>
Message-ID: <Pine.GSO.4.44.0305191717450.26639-100000@slinky.cs.nyu.edu>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 19 May 2003, David Abrahams wrote:

> I thought you might be able to help with this.  I'm having a strange
> problem invoking the "TLIB" tool (from Borland's free compiler package
> http://www.borland.com/products/downloads/download_cbuilder.html) from
> Cygwin.
>
> When you pass paths to this thing, they need to have a particular
> form.  TLIB seems to want to make everything into an option, so it
> interprets forward slashes and dashes as beginning an option, no
> matter where they appear... unless they're quoted.  Actually, It
> always takes forward slashes as option characters, but dashes have to
> be (double) quoted.  You can download this stuff and try for yourself
> if curious.
>
> Anyway, if I have to pass a path like "c:\foo-bar\baz", it works from
> the WinXP command-prompt, but not from the Cygwin command-prompt.  The
> actual use case has the command being invoked by execvp, but the bash
> shell seems to be a fine way to experiment with it.  the weird thing
> is, I built a little windows app win MSVC to print out all of its
> argv, and if I invoke it like this:
>
>       args "c:\foo-bar\baz"
>
> from either windows or cygwin, I see the same thing:
>
>      c:\foo-bar\baz
>
> I can't imagine what would make TLIB see something different, except
> *perhaps* that it's a DOS program and not a Win32 program... not that
> I have any idea how/why that has an effect.
>
> Can you shed any light on this?
>
> Many thanks in advance,
> Dave

Dave,

Have you tried compiling a small DOS program with bcc and seeing what it
would interpret its parameters as?  It might be helpful if it printed one
argument per line, or somehow indicated where the break in the arguments
happens.

Also, IIRC from my DOS hacking days, assembly programs received the whole
parameter string at once, and had to parse it themselves, so it's possible
that you have found a bug in TLIB's argument parsing routine.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton


--
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/