From: andreas@kurzegasse.de (Andreas Vögele)
To: emacs-devel@gnu.org
Subject: Re: Warning starting Emacs (Cygwin)
Date: Sun, 03 Aug 2008 08:20:58 +0200 [thread overview]
Message-ID: <874p628vqt.fsf@sophie-scholl.freifunk.kurzegasse.de> (raw)
In-Reply-To: 87wsiz1b6l.fsf@stupidchicken.com
Chong Yidong <cyd@stupidchicken.com> writes:
> Dan Nicolaescu <dann@ics.uci.edu> writes:
>
>> Unfortunately none of these ring a bell to me. Yidong I assume this
>> code is the reason you added the HAVE_GETRLIMIT autoconf check, can you
>> guess what can be wrong here?
>
> The reason I added the getrlimit check was because of the bug reported
> here (bug#86):
>
> http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=86
>
>> src/vm-limit.c has #ifdef HAVE_GETRLIMIT...#else...#endif sections
>> (i.e. line 36 onwards and line 158 onwards) and yet the configure
>> script never tests for getrlimit() and hence config.h never has any
>> HAVE_GETRLIMIT definition. Yes, configure does test for setrlimit()
>> and sets HAVE_SETRLIMIT though!
>
> Apparently, due to an oversight in the configure script, the
> HAVE_GETRLIMIT code was always turned off, even though the code had
> already been written.
>
> Could it be that getrlimit is buggy on Cygwin? Maybe we could work
> around this by turning off HAVE_GETRLIMIT on that platform :-P
BTW, NetBSD, OpenBSD and DragonFly BSD do not define RLIMIT_AS, which is
used in the #ifdef HAVE_GETRLIMIT...#else...#endif section.
DragonFLY BSD defines RLIMIT_VMEM in sys/resource.h, but doesn't mention
this limit in the getrlimit manual page.
next prev parent reply other threads:[~2008-08-03 6:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 14:45 Failure bootstrapping Emacs (Cygwin) Angelo Graziosi
2008-07-31 16:27 ` Angelo Graziosi
2008-07-31 16:57 ` Angelo Graziosi
2008-07-31 17:00 ` Dan Nicolaescu
2008-08-01 10:38 ` Warning starting Emacs (was Re: Failure bootstrapping Emacs (Cygwin)) Angelo Graziosi
2008-08-01 12:51 ` Warning starting Emacs (Cygwin) Angelo Graziosi
2008-08-01 13:08 ` Dan Nicolaescu
2008-08-01 14:13 ` Angelo Graziosi
2008-08-01 14:36 ` Dan Nicolaescu
2008-08-01 20:47 ` Angelo Graziosi
2008-08-02 4:06 ` Dan Nicolaescu
2008-08-02 14:29 ` Angelo Graziosi
2008-08-02 15:02 ` Angelo Graziosi
2008-08-02 18:59 ` Dan Nicolaescu
2008-08-02 19:14 ` Chong Yidong
2008-08-02 19:30 ` Dan Nicolaescu
2008-08-02 19:54 ` Eli Zaretskii
2008-08-02 20:19 ` Chong Yidong
2008-08-02 20:24 ` Chong Yidong
2008-08-03 3:26 ` Eli Zaretskii
2008-08-03 6:20 ` Andreas Vögele [this message]
2008-08-03 14:10 ` Chong Yidong
2008-08-03 22:35 ` Angelo Graziosi
2008-08-04 6:25 ` Andreas Vögele
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874p628vqt.fsf@sophie-scholl.freifunk.kurzegasse.de \
--to=andreas@kurzegasse.de \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).