From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org, miles@gnu.org
Subject: Re: `exec shield' test in configure too strict?
Date: Wed, 06 Oct 2004 13:16:40 +0200 [thread overview]
Message-ID: <01c4ab96$Blat.v2.2.2$19340460@zahav.net.il> (raw)
In-Reply-To: <BB337EDE-170E-11D9-8D1E-000D93505B76@swipnet.se> (jan.h.d@swipnet.se)
> From: "Jan D." <jan.h.d@swipnet.se>
> Date: Tue, 5 Oct 2004 22:40:02 +0200
> Cc: emacs-devel@gnu.org
>
> I have checked in a test that runs a program and sees if the heap start
> address is random.
Doesn't this harm cross-building Emacs? I always thought that running
a test program at configure time should be avoided, and that tests
that only compile or link programs should be peferred.
next prev parent reply other threads:[~2004-10-06 11:16 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
2004-10-06 11:16 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01c4ab96$Blat.v2.2.2$19340460@zahav.net.il' \
--to=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.