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
Date:	Thu, 8 Apr 2004 13:21:15 -0400
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Gcc/ld and long command lines (> 32k)
Message-ID:	<20040408172115.GB24612@coc.bosbc.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<Pine DOT GSO DOT 4 DOT 50 DOT 0404081719370 DOT 380-100000 AT pjakkur DOT iar DOT se> <Pine DOT LNX DOT 4 DOT 53 DOT 0404080943250 DOT 1010 AT gremlin DOT fruitbat DOT org>
Mime-Version:	1.0
In-Reply-To:	<Pine.LNX.4.53.0404080943250.1010@gremlin.fruitbat.org>
User-Agent:	Mutt/1.4.1i

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.

I would highly recommend against using this construct, however.  It's better
to use traditional unix methods for working around this problem.  Cygwin isn't
the only unix-like system out there with a measly amount of space set aside for
the command line.

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/

- Raw text -