At 11:57 AM 4/9/2004, you wrote:
>On Fri, Apr 09, 2004 at 11:28:54AM -0400, Larry Hall wrote:
>>Right. I think that goes along with the notion that the '@' stuff is
>>enabled for Cygwin processes invoked from non-Cygwin ones. But perhaps
>>I was unclear about what I was looking for. Peter's res
At 12:44 PM 4/9/2004, you wrote:
>On Fri, 9 Apr 2004, Larry Hall wrote:
>
>Hi Larry,
>
>> Right. I think that goes along with the notion that the '@' stuff is
>> enabled for Cygwin processes invoked from non-Cygwin ones. But perhaps
>> I was unclear about what I was looking for. Peter's response
wc
> > 1 1 3
> >/tmp> $(cygpath -u ${COMSPEC}) /c $(cygpath -w /bin/echo) @t | wc
> > 1 11850 404970
> >
> >But the handling of quotes is likely to be ugly.
> >
> >-Original Message-
> >From: Larry Hall
> >Sent:
On Fri, 9 Apr 2004, Larry Hall wrote:
> At 12:00 AM 4/9/2004, you wrote:
> >On Thu, 8 Apr 2004, Christopher Faylor wrote:
> >
> >> On Thu, Apr 08, 2004 at 10:07:19PM +0200, Johan Holmberg wrote:
> >> >A short description of my enironment:
> >> >
> >> >- the programs I'm building are C/C++ compiler
On Fri, Apr 09, 2004 at 11:28:54AM -0400, Larry Hall wrote:
>Right. I think that goes along with the notion that the '@' stuff is
>enabled for Cygwin processes invoked from non-Cygwin ones. But perhaps
>I was unclear about what I was looking for. Peter's response seemed to
>indicate that he tr
es is likely to be ugly.
>
>-----Original Message-----
>From: Larry Hall
>Sent: Friday, April 09, 2004 9:18 AM
>To: Peter A. Castro; [EMAIL PROTECTED]
>Subject: Re: Gcc/ld and long command lines (> 32k)
>
>At 12:00 AM 4/9/2004, you wrote:
>>On Thu, 8 Apr 2004, Chris
-w /bin/echo) @t | wc
1 11850 404970
But the handling of quotes is likely to be ugly.
-Original Message-
From: Larry Hall
Sent: Friday, April 09, 2004 9:18 AM
To: Peter A. Castro; [EMAIL PROTECTED]
Subject: Re: Gcc/ld and long command lines (> 32k)
At 12:00 AM 4/9/2004, you wr
At 12:00 AM 4/9/2004, you wrote:
>On Thu, 8 Apr 2004, Christopher Faylor wrote:
>
>> On Thu, Apr 08, 2004 at 10:07:19PM +0200, Johan Holmberg wrote:
>> >A short description of my enironment:
>> >
>> >- the programs I'm building are C/C++ compilers
>> >
>> >- I use GCC in Cygwin to get a "second opi
Ross Ridge wrote:
>
> You can try using an implicit linker script. Create a file, call it
> something like "my-ld-script", with lines like the following:
>
> INPUT(obj1.o obj2.o obj3.o)
> INPUT(obj4.o, obj5.o, obj6.o)
> INPUT(obj7.o)
>
> And then instead of linking with a
On Thu, 8 Apr 2004, Christopher Faylor wrote:
> On Thu, Apr 08, 2004 at 10:07:19PM +0200, Johan Holmberg wrote:
> >A short description of my enironment:
> >
> >- the programs I'm building are C/C++ compilers
> >
> >- I use GCC in Cygwin to get a "second opinion" from another compiler
> > than the
On Thu, Apr 08, 2004 at 10:07:19PM +0200, Johan Holmberg wrote:
>A short description of my enironment:
>
>- the programs I'm building are C/C++ compilers
>
>- I use GCC in Cygwin to get a "second opinion" from another compiler
> than the one we use normally (Visual C++).
>
>- I use Cons as my buil
> Several replies mentioned the possibility of making several
> intermediate libraries. I'm well aware of that possibility. But since
> I'm not interested in the "library functionality" of libraries, any such
> partitioning seems artificial. I always want a *full linking* where all
> object files
Christopher Faylor wrote:
> On Thu, Apr 08, 2004 at 11:11:58AM -0700, Peter A. Castro wrote:
>...
> >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:
>
>
1:45 PM
To: [EMAIL PROTECTED]
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 s
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 th
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
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 gag
> -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 t
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 c
On Thu, 8 Apr 2004, Johan Holmberg wrote:
> Hi !
>
> I tried to compile/link an application consisting of several hundred
> C/C++ files. This gives quite a long command line when it is time
> to link the application.
A smarter, more traditional, approach would be to change your makefile to
archiv
At 11:50 AM 4/8/2004, you wrote:
>Hi !
>
>I tried to compile/link an application consisting of several hundred
>C/C++ files. This gives quite a long command line when it is time
>to link the application.
>
>Windows seem to have a limit of 32k for the length of the command
>line as given to to the
21 matches
Mail list logo
