From: Christopher Faylor <cgf-rcm@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Strange make [Error 255] (cygwin bug?)
Date: Sat, 27 Sep 2003 16:11:00 -0000 [thread overview]
Message-ID: <20030927160941.GE19912@redhat.com> (raw)
In-Reply-To: <87n0cql48x.fsf@peder.flower>
On Sat, Sep 27, 2003 at 04:01:34PM +0200, Jan Nieuwenhuizen wrote:
>Corinna Vinschen writes:
>>>How does it make it unnecessary? Won't it still cause make to return
>>>an error as opposed to actually getting make working?
>>
>>Yes, but it returns a correct, useful error message. Obviously there
>>is a system imposed upper limit of command line length on all systems,
>>even if it's 256MB or whatever. So relying on these overlong command
>>lines is highly non-portable anyway and at least Cygwin now returns the
>>correct message if it comes to that.
>
>Hmm, maybe you're right and we should fix the installation process, but
>this is the first problem we heard of. If it's really that highly
>non-portable, then Cygwin is the least obscure UNIX system that doesn't
>grok this :-)
There have certainly been other "UNIXes" out there which had small
command line length limits. Early AT&T System V releases come to mind.
Probably 32K is not a common limit anymore, though.
One of the reasons I went to the considerable work of implementing the
-X option was to bypass arbitrary limits like this and to bypass the
command line parsing that Windows enforces. Binaries mounted with -X
pass arguments around in an argv list, just like UNIX. So, while the
limits still exist, they should be much larger than what Windows uses.
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/
next prev parent reply other threads:[~2003-09-27 16:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000b01c382de$67fb2a10$8006fea9@bertigep>
2003-09-24 21:20 ` Igor Pechtchanski
2003-09-24 22:05 ` Fodor Bertalan
2003-09-24 22:18 ` Igor Pechtchanski
2003-09-25 7:30 ` Fodor Bertalan
2003-09-25 12:46 ` Igor Pechtchanski
2003-09-25 13:12 ` Corinna Vinschen
2003-09-25 13:40 ` Igor Pechtchanski
2003-09-25 13:41 ` Corinna Vinschen
2003-09-25 13:54 ` Christopher Faylor
2003-09-25 15:50 ` Bertalan Fodor
2003-09-26 8:54 ` Corinna Vinschen
2003-09-26 15:28 ` Christopher Faylor
2003-09-26 18:02 ` Corinna Vinschen
2003-09-27 14:05 ` Jan Nieuwenhuizen
2003-09-27 16:11 ` Christopher Faylor [this message]
2003-09-26 8:38 ` Jan Nieuwenhuizen
2003-09-26 8:48 ` Corinna Vinschen
2003-09-26 15:27 ` Christopher Faylor
2003-09-25 13:44 ` Make error 255 bug Fodor Bertalan
2003-09-24 9:45 Strange make [Error 255] (cygwin bug?) Fodor Bertalan
2003-09-24 18:27 ` Igor Pechtchanski
2003-09-24 18:10 ` Fodor Bertalan
2003-09-24 18:12 ` Fodor Bertalan
2003-09-24 19:47 ` Igor Pechtchanski
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=20030927160941.GE19912@redhat.com \
--to=cgf-rcm@cygwin.com \
--cc=cygwin@cygwin.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).