On 9/18/20 2:01 AM, Bruno Haible wrote:
The file descriptor 2 is unaffected by the file descriptor
reshuffle. Only file descriptor 6 is affected, which is the one used by
AC_MSG_CHECKING/AC_MSG_RESULT. No one is supposed to use this file descriptor
in a 'trap' action.
Ah, sorry, I misread it.
Hi Paul,
> On 9/17/20 1:53 PM, Bruno Haible wrote:
> > - {
> > -$1
> > - } AS_MESSAGE_FD>/dev/null
> > + exec GL_TMP_FD>&AS_MESSAGE_FD AS_MESSAGE_FD>/dev/null
> > + $1
> > + exec AS_MESSAGE_FD>&GL_TMP_FD AS_MESSAGE_FD>&-
I had a typo in here. Corrected:
exec GL_TMP_FD>&AS_MESSAGE_FD A
On 9/17/20 1:53 PM, Bruno Haible wrote:
- {
-$1
- } AS_MESSAGE_FD>/dev/null
+ exec GL_TMP_FD>&AS_MESSAGE_FD AS_MESSAGE_FD>/dev/null
+ $1
+ exec AS_MESSAGE_FD>&GL_TMP_FD AS_MESSAGE_FD>&-
If a trap occurs during $1 and 'configure' outputs something to stderr before it
exits, the output
On Solaris 10, the configuration aborts:
$ ../configure
...
checking for raise... yes
checking for sigprocmask...
../configure: test: argument expected
The reason is that gl_cv_func_sigprocmask_v16 is not set in the statement
if test $gl_cv_func_sigprocmask_v16 != yes; then
(signalbl
