From mboxrd@z Thu Jan  1 00:00:00 1970
Path: main.gmane.org!not-for-mail
From: Richard Stallman <rms@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: lim_data too narrow
Date: Sun, 21 Dec 2003 23:07:56 -0500
Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org
Message-ID: <E1AYHMK-0005K1-Du@fencepost.gnu.org>
References: <200312180058.hBI0wtaq054209@bigtex.jrv.org>
Reply-To: rms@gnu.org
NNTP-Posting-Host: deer.gmane.org
X-Trace: sea.gmane.org 1072066556 6987 80.91.224.253 (22 Dec 2003 04:15:56 GMT)
X-Complaints-To: usenet@sea.gmane.org
NNTP-Posting-Date: Mon, 22 Dec 2003 04:15:56 +0000 (UTC)
Cc: emacs-devel@gnu.org
Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Dec 22 05:15:53 2003
Return-path: <emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org>
Original-Received: from quimby.gnus.org ([80.91.224.244])
	by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian))
	id 1AYHU1-0001gz-00
	for <emacs-devel@deer.gmane.org>; Mon, 22 Dec 2003 05:15:53 +0100
Original-Received: from monty-python.gnu.org ([199.232.76.173])
	by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian))
	id 1AYHU1-0000mM-00
	for <emacs-devel@quimby.gnus.org>; Mon, 22 Dec 2003 05:15:53 +0100
Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org)
	by monty-python.gnu.org with esmtp (Exim 4.24)
	id 1AYINC-00022V-59
	for emacs-devel@quimby.gnus.org; Mon, 22 Dec 2003 00:12:54 -0500
Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24)
	id 1AYIMo-000224-H8
	for emacs-devel@gnu.org; Mon, 22 Dec 2003 00:12:30 -0500
Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24)
	id 1AYIMI-0001tx-3K
	for emacs-devel@gnu.org; Mon, 22 Dec 2003 00:12:29 -0500
Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org)
	by monty-python.gnu.org with esmtp (Exim 4.24) id 1AYIMH-0001th-3C
	for emacs-devel@gnu.org; Mon, 22 Dec 2003 00:11:57 -0500
Original-Received: from rms by fencepost.gnu.org with local (Exim 4.24)
	id 1AYHMK-0005K1-Du; Sun, 21 Dec 2003 23:07:56 -0500
Original-To: James Van Artsdalen <james@jrv.org>
In-reply-to: <200312180058.hBI0wtaq054209@bigtex.jrv.org> (message from James
	Van Artsdalen on Wed, 17 Dec 2003 18:58:55 -0600 (CST))
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Emacs development discussions.  <emacs-devel.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org
Xref: main.gmane.org gmane.emacs.devel:18787
X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18787

    lim_data needs to be at least as wide as the rlimit .rlim_cur field or
    truncation occurs.

It would seem that on a 64-bit machine, lim_data should
be a 64-bit type.  Is there any agreement on how to
specify such a type in C?

We could use configure to check whether rlim_t is defined
in some header file.  What header file should it be in?