From: Miles Bader <miles@lsi.nec.co.jp>
Cc: Stefan <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: `exec shield' test in configure too strict?
Date: Wed, 06 Oct 2004 16:56:31 +0900 [thread overview]
Message-ID: <buovfdocma8.fsf@mctpc71.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <4163A3A8.1030804@swipnet.se> (Jan D.'s message of "Wed, 06 Oct 2004 09:50:00 +0200")
"Jan D." <jan.h.d@swipnet.se> writes:
>>>I.e. just transform the current error into a warning.
>>
>> I'd suggest this as the short-term fix. It can use appropriately big
>> letters or whitespace or whatever, to be noticeable.
>
> I've used some withespace and some '***' to make it stand out. But it
> still flashes by very fast on a reasonable new machine, so unless you
> are looking at the configure output (I usually don't) you probably
> will miss it.
How about outputting it again/instead at the end of the configure output
(after it prints the summary of the configuration); then it should be
just before the user's prompt.
-Miles
--
"Unless there are slaves to do the ugly, horrible, uninteresting work, culture
and contemplation become almost impossible. Human slavery is wrong, insecure,
and demoralizing. On mechanical slavery, on the slavery of the machine, the
future of the world depends." -Oscar Wilde, "The Soul of Man Under Socialism"
next prev parent reply other threads:[~2004-10-06 7:56 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 [this message]
2004-10-06 11:31 ` Jan D.
2004-10-06 7:48 ` Jan D.
2004-10-06 12:58 ` Stefan Monnier
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=buovfdocma8.fsf@mctpc71.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).