Mail Archives: cygwin/2004/04/08/14:34:41
This behavior is documented:
http://sources.redhat.com/cygwin/cygwin-ug-net/using-specialnames.html#AEN89
9
As for escaping @, experimenting with c:\cygwin\bin\echo will probably give
an answer.
-----Original Message-----
From: Dave Korn [mailto:dk AT artimi DOT com]
Sent: Thursday, April 08, 2004 1:45 PM
To: cygwin AT cygwin DOT com
Subject: RE: Gcc/ld and long command lines (> 32k)
> -----Original Message-----
> From: cygwin-owner On Behalf Of Christopher Faylor
> Sent: 08 April 2004 18:21
> On Thu, Apr 08, 2004 at 10:00:56AM -0700, Peter A. Castro wrote:
> >The @filename syntax is used by MS's linker (Visual
> C++/Studio). To my
> >knowledge gcc's linker doesn't support this syntax.
>
> The cygwin DLL supports it (implemented over my gagged and
> thrashing body)
> but only at a non-cygwin-shell command prompt, e.g.,
>
> c:\>gcc -o foo @foo.blah
>
> works
>
> but
>
> bash$ gcc -o foo @foo.blah
>
> doesn't.
Yow. The *DLL* expands that? Eww. I understand why you had to be tied
down, that's soooo the wrong place for it. WRS implemented it into their
versions of the binutils, which seems like the right place for it. Maybe
getopts should understand it. Perhaps even bash. But putting it in the
DLL? <gag!>
Can I at least escape the @ sign if I really do want to pass "@word" as an
argv entry? I like to use parameters with an @ char prefixing them in my
own tools, and I don't want the parameter to suddenly be replaced by the
contents of a file that happens to have the same name....!
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
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 -