This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Gcc/ld and long command lines (> 32k)
On Thu, Apr 08, 2004 at 11:11:58AM -0700, Peter A. Castro wrote:
>On Thu, 8 Apr 2004, Christopher Faylor wrote:
>>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.,
>
>Good Gravy!! Yikes!! *Tell me* this is a late April Fool's joke!!
>Please!!
Nope, it's true. I'm sure glad I added the "gagged and thrashing"
comment. :-)
>> 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.
>
>The original post doesn't specify weither they are working inside of or
>outside of a Cygwin environment, but from some of the comments I kinda
>think it maybe outside of. Something like:
For some reason, I assumed they were running from make, where the '@' wouldn't
be exercised. But you are right, that isn't clear.
>On Thu, 8 Apr 2004, Johan Holmberg wrote:
>> Is ld.exe not interpreting the special "@" like other
>> Cygwin programs ?
>
>Kinda makes me think he's running this from outside of any Cygwin shell.
>
>But, my original suggestion, as well as your mention above, still stands:
>use traditional unix methods, like static-link archive libraries.
>Related to, but just as problematic, would be turning all of those object
>files into a shared-library/DLL, which I encourage the original poster to
>also consider if this program is ment to be run concurrently.
Right. Larry's pointer to another one of my messages should also work
around the problem by making cygwin use internal methods for passing
arguments. This might be enough to get things working but it is not
foolproof. Using the above techniques is a much better plan.
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/