Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 8 Apr 2004 13:21:15 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Gcc/ld and long command lines (> 32k) Message-ID: <20040408172115.GB24612@coc.bosbc.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: 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 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/