Akim Demaille | 1 Aug 2002 14:22
Picon
Picon
Favicon

Re: Bug#154053: sendmailconfig fails due to m4 problems on Linux 2.0.x (fwd)


| Hello.
| I've received the following report from the Debian Bug System.
| 
| By looking at some m4 web pages, it seems to be a known problem.
| Is there a workaround, other than upgrading to Linux 2.2.x or later?
| 
| For example, if the configure script is changed so that it does not
| check for sigaltstack and sigstack:
| 
| --- configure.orig	Mon Jul 29 18:09:44 2002
| +++ configure	Mon Jul 29 18:09:57 2002
|  <at>  <at>  -1160,7 +1160,7  <at>  <at> 
|  fi
| 
| 
| -for ac_func in mkstemp sigaction sigaltstack sigstack sigvec strerror tmpfile
| +for ac_func in mkstemp sigaction sigvec strerror tmpfile
|  do
|  echo $ac_n "checking for $ac_func""... $ac_c" 1>&4
|  if eval "test \"`echo '${'ac_cv_func_$ac_func'+set}'`\" = set"; then
| 
| would the resulting m4 executable work reliably on every glibc-based system?

I would recommend to fix the AC_CHECK_FUNC invocation to

AC_CHECK_FUNCS([[sigstack]])
Santiago Vila | 4 Aug 2002 17:16
Picon
Favicon

Re: Bug#154053: sendmailconfig fails due to m4 problems on Linux 2.0.x (fwd)

Akim Demaille wrote:
> | I've received the following report from the Debian Bug System.
> |
> | By looking at some m4 web pages, it seems to be a known problem.
> | Is there a workaround, other than upgrading to Linux 2.2.x or later?
> |
> | For example, if the configure script is changed so that it does not
> | check for sigaltstack and sigstack:
> |
> | --- configure.orig	Mon Jul 29 18:09:44 2002
> | +++ configure	Mon Jul 29 18:09:57 2002
> |  <at>  <at>  -1160,7 +1160,7  <at>  <at> 
> |  fi
> |
> |
> | -for ac_func in mkstemp sigaction sigaltstack sigstack sigvec strerror tmpfile
> | +for ac_func in mkstemp sigaction sigvec strerror tmpfile
> |  do
> |  echo $ac_n "checking for $ac_func""... $ac_c" 1>&4
> |  if eval "test \"`echo '${'ac_cv_func_$ac_func'+set}'`\" = set"; then
> |
> | would the resulting m4 executable work reliably on every glibc-based system?
>
> I would recommend to fix the AC_CHECK_FUNC invocation to
>
> AC_CHECK_FUNCS([[sigstack]])

What do you mean, exactly? If I apply this patch:

--- ../m4-1.4.orig/configure.in	1994-11-06 04:40:38.000000000 +0100
(Continue reading)


Gmane