From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: andreas@kurzegasse.de (Andreas =?iso-8859-1?Q?V=F6gele?=) Newsgroups: gmane.emacs.devel Subject: Re: Warning starting Emacs (Cygwin) Date: Sun, 03 Aug 2008 08:20:58 +0200 Message-ID: <874p628vqt.fsf@sophie-scholl.freifunk.kurzegasse.de> References: <4891D01B.6070802@alice.it> <4891E7E8.1000503@alice.it> <200807311700.m6VH0eCa004994@sallyv1.ics.uci.edu> <4892E7BE.1080706@alice.it> <489306EE.7090800@alice.it> <200808011308.m71D8PA3023871@sallyv1.ics.uci.edu> <489319F7.5040101@alice.it> <200808011436.m71EaAeZ019293@sallyv1.ics.uci.edu> <4893765E.5020803@alice.it> <200808020406.m7246D1T003058@sallyv1.ics.uci.edu> <48946F36.3020505@alice.it> <200808021859.m72IxGnr000877@sallyv1.ics.uci.edu> <87wsiz1b6l.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1217744720 15555 80.91.229.12 (3 Aug 2008 06:25:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 3 Aug 2008 06:25:20 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Aug 03 08:26:11 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KPX2g-0004hr-Jy for ged-emacs-devel@m.gmane.org; Sun, 03 Aug 2008 08:26:10 +0200 Original-Received: from localhost ([127.0.0.1]:41614 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KPX1l-0008VY-6Q for ged-emacs-devel@m.gmane.org; Sun, 03 Aug 2008 02:25:13 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KPX1f-0008Rv-3N for emacs-devel@gnu.org; Sun, 03 Aug 2008 02:25:07 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KPX1d-0008PD-VY for emacs-devel@gnu.org; Sun, 03 Aug 2008 02:25:06 -0400 Original-Received: from [199.232.76.173] (port=34630 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KPX1d-0008Op-J9 for emacs-devel@gnu.org; Sun, 03 Aug 2008 02:25:05 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:38192 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KPX1d-00054t-7Q for emacs-devel@gnu.org; Sun, 03 Aug 2008 02:25:05 -0400 Original-Received: from root by ciao.gmane.org with local (Exim 4.43) id 1KPX1b-0006Dx-1Y for emacs-devel@gnu.org; Sun, 03 Aug 2008 06:25:03 +0000 Original-Received: from hsi-kbw-091-089-179-062.hsi2.kabel-badenwuerttemberg.de ([91.89.179.62]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 03 Aug 2008 06:25:03 +0000 Original-Received: from andreas by hsi-kbw-091-089-179-062.hsi2.kabel-badenwuerttemberg.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 03 Aug 2008 06:25:03 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 31 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: hsi-kbw-091-089-179-062.hsi2.kabel-badenwuerttemberg.de User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) Cancel-Lock: sha1:X7ONLFFxI5JbXfdL8rPtOylh77M= X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:101992 Archived-At: Chong Yidong writes: > Dan Nicolaescu 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.