From: Brendan Simon <brendan@dgs.monash.edu.au>
To: Roger Cruz <rogerc@ignitus.com>
Cc: gdb@sourceware.cygnus.com, cygwin@sourceware.cygnus.com
Subject: Re: Can't build GDB 4.18 under Cygnus 2.0.1
Date: Sat, 31 Jul 1999 18:34:00 -0000 [thread overview]
Message-ID: <378E940E.438615B4@dgs.monash.edu.au> (raw)
Message-ID: <19990731183400.ktJG6PKoEzZphUgIFxPzA2YNgS8wF-M_-DSfu2ur8YM@z> (raw)
In-Reply-To: <378E8479.8154C6E5@ignitus.com>
Roger Cruz wrote:
> I think I have narrowed down the problem of building GDB 4.18 with CygWin 20.1. It
> appears to be that the maximum command line has been exceeded. The line as shown
> below has 615 characters. If I start removing directory names, it works fine when
> the number is brought down to 412. Is there any way that I can get around this
> problem? Does CygWin allow you to control the maximum line length?
>
> Any ideas are welcome. I'm anxious to get this building on a PC so I can work from
> home!
> Thanks.
> Roger
What are you using for your shell (bash, command.com or cmd.exe) ?
If you are not using bash, then I advise you to try it. If you don't want a unix type
shell then you will have to try another alternative to the M$ shells.
If you are using bash, then I don't know what your alternatives are. It might be a
limitiation in the executables that are being invoked ?
Brendan Simon.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-07-31 18:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <378DF57E.3D26CA78@ignitus.com>
[not found] ` <378E4F06.2942CB1C@ignitus.com>
1999-07-15 17:57 ` Roger Cruz
1999-07-15 19:09 ` Brendan Simon [this message]
1999-07-31 18:34 ` Brendan Simon
1999-07-18 12:53 ` Roger Cruz
1999-07-19 11:50 ` Stan Shebs
1999-07-31 18:34 ` Stan Shebs
1999-07-31 18:34 ` Roger Cruz
1999-07-31 18:34 ` Roger Cruz
1999-07-16 7:47 Roger Cruz
1999-07-31 18:34 ` Roger Cruz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=378E940E.438615B4@dgs.monash.edu.au \
--to=brendan@dgs.monash.edu.au \
--cc=cygwin@sourceware.cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=rogerc@ignitus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).