`exec shield' test in configure too strict?

[Miles Bader <miles@lsi.nec.co.jp>]

Recently Emacs' configure script has been changed to check for the
presence of linux `exec shield' functionality, by looking for the file
/proc/sys/kernel/exec-shield, and seeing if it as a non-zero value.  If
it is present and enabled, and there's no `setarch' program available,
configure will give an error message and abort.  The reason for this, as
I understand it, is that emacs cannot dump on such a system unless it
can use the `setarch' program.

However this test seems too strict:  On fencepost.gnu.org, exec-shield
is enabled:

   $ cat /proc/sys/kernel/exec-shield
   1

and there is no setarch program:

   $ type setarch
   bash: type: setarch: not found

and so emacs refuses to configure -- but if disable this test by doing:

   $ make ac_cv_file__proc_sys_kernel_exec_shield=no

Then Emacs configures and dumps just fine, despite not using `setarch'.

Perhaps a warning (maybe in big letters) rather than a fatal error would
be appropriate.

Oh, BTW:

   $ cat /proc/version
   Linux version 2.6.7-1.494.2.2smp (bhcompile@tweety.build.redhat.com) (gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 SMP Tue Aug 3 09:59:49 EDT 2004

A bit odd that fencepost is running a Redhat kernel when it's a Debian
system but whatever... :-)

Thanks,

-Miles
-- 
If you can't beat them, arrange to have them beaten.  [George Carlin]