[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Warning starting Emacs (Cygwin)

From: Andreas Vögele
Subject: Re: Warning starting Emacs (Cygwin)
Date: Sun, 03 Aug 2008 08:20:58 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix)

Chong Yidong <address@hidden> writes:

> Dan Nicolaescu <address@hidden> 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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]