Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Thu, 8 Apr 2004 14:26:49 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Gcc/ld and long command lines (> 32k) Message-ID: <20040408182649.GF24612@coc.bosbc.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20040408172115 DOT GB24612 AT coc DOT bosbc DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Thu, Apr 08, 2004 at 06:45:01PM +0100, Dave Korn wrote: >> -----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? I think maybe DJGPP does things that way so there was precedent for it. >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....! Quoting the @ defeats it. Probably \@ does too. And, just using a cygwin shell (ash, bash, tcsh, zsh) for everything bypasses that code entirely. cgf -- 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/