From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: `exec shield' test in configure too strict?
Date: Wed, 06 Oct 2004 08:58:41 -0400 [thread overview]
Message-ID: <jwvu0t8vwex.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4163A343.7060103@swipnet.se> (Jan D.'s message of "Wed, 06 Oct 2004 09:48:19 +0200")
>> We can output the message even if the build succeeds.
> You lost me, what message? The one in configure or the hypotetical new one
> after temacs dumps core?
I expect the message would be the same in either case (more or less), so
I just said "the" message.
>> I.e. just transform the current error into a warning.
> I've done that.
Thanks.
> You maybe never built Emacs on a machine where the build takes 20 minutes :-)
Believe me, I've done my share of building Emacs on slow machines.
> If exec-shield and/or its effects, like randomized heap start, becomes more
> widespread this will be a very common case. I would not be surprised if
> something like it will be incorporated in to the Linux kernel proper, and
> not just for Fedora as it is now (and some unofficial Debian patches seems
> to exist).
If that's the case, then an error message (no matter how good) is *not* the
answer. We simply do not want to go down that road: Emacs should "just
work" at least in normal (i.e. common) circumstances.
Stefan
next prev parent reply other threads:[~2004-10-06 12:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 5:53 `exec shield' test in configure too strict? Miles Bader
2004-10-04 15:04 ` Jan D.
2004-10-04 21:20 ` Miles Bader
2004-10-04 21:37 ` Jan D.
2004-10-05 20:40 ` Jan D.
2004-10-05 21:44 ` Stefan Monnier
2004-10-05 22:11 ` Jan D.
2004-10-06 0:18 ` Stefan
2004-10-06 1:34 ` Miles Bader
2004-10-06 7:50 ` Jan D.
2004-10-06 7:56 ` Miles Bader
2004-10-06 11:31 ` Jan D.
2004-10-06 7:48 ` Jan D.
2004-10-06 12:58 ` Stefan Monnier [this message]
2004-10-06 11:16 ` Eli Zaretskii
2004-10-06 11:38 ` Jan D.
2004-10-07 15:44 ` Camm Maguire
2004-10-07 16:44 ` Richard Stallman
2004-10-07 18:16 ` Jan D.
2004-10-09 1:25 ` Richard Stallman
2004-10-11 10:30 ` Jan D.
2004-10-12 8:56 ` Richard Stallman
2004-10-20 20:33 ` Jan D.
2004-10-21 13:57 ` Richard Stallman
2004-10-22 21:02 ` Camm Maguire
2004-10-25 19:05 ` Jan D.
2004-10-26 20:24 ` Camm Maguire
2004-10-27 10:48 ` Richard Stallman
2004-10-27 12:17 ` Jan D.
2004-11-06 17:00 ` other unexec problems Camm Maguire
2004-11-09 7:58 ` Jan D.
2004-10-05 18:04 ` `exec shield' test in configure too strict? Richard Stallman
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=jwvu0t8vwex.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=miles@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).