From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 18238@debbugs.gnu.org, rrt@sc3d.org
Subject: bug#18238: Fix for DOS build when using more accurate config[.h].in
Date: Sat, 23 Oct 2021 09:18:54 +0300 [thread overview]
Message-ID: <831r4c6z75.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmz1=ZaG_-_BE5kX8gXVRo-oAWvdjXpfFaWegmfmXhFaQ@mail.gmail.com> (message from Stefan Kangas on Fri, 22 Oct 2021 15:02:17 -0400)
tags 18238 wontfix
close 18238
thanks
> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 22 Oct 2021 15:02:17 -0400
> Cc: 18238@debbugs.gnu.org
>
> Reuben Thomas <rrt@sc3d.org> writes:
>
> > DJGPP does actually have getrlimit. The special config[.h].in for MSDOS lies and says it hasn't. However, this is a white lie, because
> > getrlimit on DJGPP doesn't support RLIMIT_AS/RLIMIT_DATA, which is what we want, so we still want the workaround code. The following
> > patch simply reverses the order of a couple of tests in vm-limit.c so that being on MSDOS overrides HAVE_GETRLIMIT.
> >
> > Is it OK to install?
>
> (That was in 2014.)
>
> It seems like this patch was never installed. Is it still relevant?
It's as relevant as it was back then, but I see no reason to make a
change with no actual functionality changes, just so the world knows
that DJGPP does have (a limited version of) getrlimit. So I'm closing
this bug (after fixing the typo pointed by Andreas).
Thanks.
prev parent reply other threads:[~2021-10-23 6:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 16:47 bug#18238: Fix for DOS build when using more accurate config[.h].in Reuben Thomas
2014-08-10 16:52 ` Andreas Schwab
2014-08-10 16:53 ` Reuben Thomas
2014-08-10 17:59 ` Stefan Monnier
2014-08-10 18:05 ` Eli Zaretskii
2014-08-10 18:20 ` Reuben Thomas
2014-08-10 18:28 ` Eli Zaretskii
2014-08-10 19:35 ` Eli Zaretskii
2021-10-22 19:02 ` Stefan Kangas
2021-10-22 21:14 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-23 6:18 ` Eli Zaretskii [this message]
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=831r4c6z75.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18238@debbugs.gnu.org \
--cc=rrt@sc3d.org \
--cc=stefan@marxist.se \
/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).