This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Gcc/ld and long command lines (> 32k)
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 seemed to
> indicate that he tried *both* the suggested mount option and the '@file'
> option simultaneously. It also wasn't clear whether he was using the
> '@file' option as invoked by a Windows process (perhaps even as a variant
> of Barry's example below) or whether he tried it from a Cygwin process
> (directly). Ditto for the mount option. I think Peter was trying to
> indicate that these options work but it's a little confusing given that
> Chris's previous statements say that '@file' should be a solution for
> Windows processes and the mount option should be a solution for Cygwin
> processes. It's unclear whether Peter is confirming or refuting any
> part or parts of Chris' statement. That's what I was hoping to get some
> clarification on.
I've already responded with a more clear explaination, but I felt
compelled to respond here as well. I was making a mental leap in my
other email. Johan's original email questioned about the "-X" mount
option possibly being useful, and Chris's email talked about @file being
only useable from a non-Cygwin invocation. I tied the two together and
they worked. This is what Johan had originally asked about (both -X and
@file), and, from that context, I was responding. Sorry if it was a
little inarticulate by arrived at a conclusion without supplying my
work-sheet as proof :). For Johan's configuration, this combination
should work for him. I hadn't tried any other combinations because it
was uninteresting with respect to Johan's configuration. If it didn't
work, I would have experimented further, but it did and I didn't :)
> Larry
>
>
>
> At 11:05 AM 4/9/2004, you wrote:
> >For the record, the immediate parent can be a DOS/Windows program that is
> >itself called by a Cygwin program (in this example, bash).
> >
> >/tmp> wc t
> > 1 11850 404970 t
> >/tmp> /bin/echo @t
> >@t
> >/tmp> /bin/echo @t | 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: Friday, April 09, 2004 9:18 AM
> >To: Peter A. Castro; cygwin@cygwin.com
> >Subject: Re: Gcc/ld and long command lines (> 32k)
> >
> >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 opinion" from another compiler
> >>> > than the one we use normally (Visual C++).
> >>> >
> >>> >- I use Cons as my build tool (a Perl program).
> >>> > I use ActiveState Perl (not Cygwin Perl).
> >>> >
> >>> >So yes, I'm working "outside a Cygwin environment".
> >>>
> >>> Ok, so, sorry, but I wasn't thinking clearly. The '-X' option to mount
> >>> only works when a cygwin programs which invoke another cygwin program.
> >>> If you have a normal windows program running a cygwin program, your only
> >>> option for a longer command line is (shudder) '@'.
> >>
> >>Well, Chris, for better or worst, this "feature" does seem to work. I
> >>did a quick test of this using an @file which is 81k long and it works!
> >>You will need to remount both /usr/bin and /usr/lib with the "--system
> >>--binary -X" options. Then put your list of objects into @file and run
> >>gcc @file.
> >>For the record, I still feel that a better practice is to do archiving of
> >>object files and link with the library, but if this gets you going, this
> >>time, more power to ya.
> >
> >But wait. You're mixing advice (Chris's) it seems. He said @file would
> >be a solution if you were working outside of Cygwin shells and that
> >remounting with -X could be a solution if you were inside. So it sounds
> >like you tried both, and perhaps together, but it's unclear whether you
> >ran your tests from a Cygwin shell prompt, a Windows DOS prompt, or both.
> >Can you clarify what you tried and where?
> >
> >Thanks,
> >
> >--
> >Larry Hall http://www.rfk.com
> >RFK Partners, Inc. (508) 893-9779 - RFK Office
> >838 Washington Street (508) 893-9889 - FAX
> >Holliston, MA 01746
> >
> >--
> >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/
>
>
> --
> 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/
>
--
Peter A. Castro <doctor@fruitbat.org> or <Peter.Castro@oracle.com>
"Cats are just autistic Dogs" -- Dr. Tony Attwood
--
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/