From: Philippe Troin <phil@fifi.org>
To: zsh-workers@sunsite.dk
Subject: Spring patch clean-up: HAVE_BROKEN_TCSETPGRP and backgrounded ./configure
Date: 28 May 2004 16:55:51 -0700 [thread overview]
Message-ID: <87brk8ayyg.fsf@ceramic.fifi.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
This patch was discussed here:
http://www.zsh.org/cgi-bin/mla/redirect?usernumber=6812
Executive summary:
1. some people have complained that running zsh's configure in the
background hangs when checking for broken tcsetpgrp().
2. some people have complained that if they run zsh's configure a
some magic build script that does not have a controlling tty, then
zsh is built incorrectly (tcsetpgrp() is then assumed broken).
- this patch takes care of #1 by blocking SIGTTOU during the duration
of the "checking for broken tcsetpgrp" test.
- this patch takes care of #2 by adding a new ./configure option
--with-tcsetpgrp, which behaves this way:
* under normal circumstances (running with a ctty), this option
is not needed.
* ./configure will abort and report "Try running configure with
--with-tcsetpgrp or --without-tcsetpgrp" if this option is
needed (running WITHOUT a ctty).
* when --with-tcsetpgrp is specified, the "checking for broken
tcsetpgrp" test is skipped.
* when --without-tcsetpgrp is specified, the "checking for broken
tcsetpgrp" test is skipped and BROKEN_TCSETPGRP is AC_DEFINED.
Shall we consider this for inclusion?
Phil.
Patch against latest CVS sources:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: broken-tcsetpgrp.patch --]
[-- Type: text/x-patch, Size: 2226 bytes --]
Index: configure.ac
===================================================================
RCS file: /cvsroot/zsh/zsh/configure.ac,v
retrieving revision 1.17
diff -b -u -r1.17 configure.ac
--- configure.ac 6 Apr 2004 09:25:17 -0000 1.17
+++ configure.ac 28 May 2004 23:02:59 -0000
@@ -1766,24 +1766,53 @@
dnl -----------
AH_TEMPLATE([BROKEN_TCSETPGRP],
[Define to 1 if tcsetpgrp() doesn't work, ie BeOS R4.51.])
-if test -t 0 && test $ac_cv_func_tcsetpgrp = yes; then
+AC_ARG_WITH(tcsetpgrp,
+[ --with-tcsetpgrp assumes that tcsetpgrp() exists and works correctly],[
+case "x$withval" in
+ xyes) zsh_working_tcsetpgrp=yes;;
+ xno) zsh_working_tcsetpgrp=no;;
+ *) AC_ERROR([please use --with-tcsetpgrp=yes or --with-tcsetpgrp=no]);;
+esac],[zsh_working_tcsetpgrp=check])
+if test "x$ac_cv_func_tcsetpgrp" = xyes; then
+case "x$zsh_working_tcsetpgrp" in
+ xcheck)
+ trap "" SIGTTOU > /dev/null 2>&1 || :
AC_CACHE_CHECK(if tcsetpgrp() actually works,
zsh_cv_sys_tcsetpgrp,
[AC_TRY_RUN([
#include <sys/types.h>
#include <unistd.h>
+#include <fcntl.h>
main() {
+ int fd;
int ret;
- ret=tcsetpgrp(0, tcgetpgrp(0));
- exit(ret<0);
+ fd=open("/dev/tty", O_RDWR);
+ if (fd < 0) exit(2);
+ ret=tcsetpgrp(fd, tcgetpgrp(fd));
+ if (ret < 0) exit(1);
+ exit(0);
}
],
- zsh_cv_sys_tcsetpgrp=yes,
- zsh_cv_sys_tcsetpgrp=no,
- zsh_cv_sys_tcsetpgrp=yes)])
- if test $zsh_cv_sys_tcsetpgrp = no; then
- AC_DEFINE(BROKEN_TCSETPGRP)
- fi
+ zsh_cv_sys_tcsetpgrp=yes, [
+case $? in
+ 1) zsh_cv_sys_tcsetpgrp=no;;
+ 2) zsh_cv_sys_tcsetpgrp=notty;;
+ *) zsh_cv_sys_tcsetpgrp=error;;
+esac
+ ], zsh_cv_sys_tcsetpgrp=yes)])
+ case "x$zsh_cv_sys_tcsetpgrp" in
+ xno) AC_DEFINE(BROKEN_TCSETPGRP);;
+ xyes) :;;
+ xnotty) AC_MSG_ERROR([no controlling tty
+Try running configure with --with-tcsetpgrp or --without-tcsetpgrp]);;
+ *) AC_MSG_ERROR([unexpected return status]);;
+ esac
+ trap - SIGTTOU > /dev/null 2>&1 || :
+ ;;
+ xyes) :;;
+ xno) AC_DEFINE(BROKEN_TCSETPGRP);;
+ *) AC_MSG_ERROR([unexpected value zsh_working_tcsetpgrp=$zsh_working_tcsetpgrp]);;
+esac
fi
dnl -----------
next reply other threads:[~2004-05-28 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 23:55 Philippe Troin [this message]
2004-06-02 9:25 ` Peter Stephenson
2004-06-02 9:43 ` Philippe Troin
2004-06-08 13:27 ` Peter Stephenson
2004-06-08 15:05 ` Philippe Troin
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=87brk8ayyg.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=zsh-workers@sunsite.dk \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).