From: Jens Petersen <petersen@redhat.com>
To: Zsh-users <zsh-users@sunsite.dk>
Subject: problem building zsh in background
Date: Tue, 25 Nov 2003 17:17:59 +0900 [thread overview]
Message-ID: <m3d6bgq2tk.wl%petersen@redhat.com> (raw)
Any comments on this bug report:
<https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=102042>?
It seems easy to reproduce with both 4.0.7 and 4.1.1: eg
% rm -rf zsh-4.0.7
% tar tar jxf zsh-4.0.7.tar.bz2
% cd zsh-4.0.7
% ./configure &
:
:
checking if kill(pid, 0) returns ESRCH correctly... yes
checking if POSIX sigsuspend() works... yes
checking if tcsetpgrp() actually works...
[1] + suspended (tty output) ./configure
In the above report Roland McGrath comments "The zsh
configure script runs a program that does tcsetpgrp on fd 0
(stdin), which is broken in multiple ways. If the input
were redirected then the test would give a false negative.
Since the input is your terminal and the job is in the
background, it rightly gets SIGTTOU for trying to perform
tcsetpgrp. The only way a test of this nature can be safe
is if it's done on a specially created pty, e.g. in the
child of a forkpty call, but using ptys is not fully
portable so zsh is kind of stuck here."
Anyone looked into this before?
Jens
next reply other threads:[~2003-11-25 8:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 8:17 Jens Petersen [this message]
2003-11-25 20:39 ` Philippe Troin
2003-11-26 8:57 ` Jens Petersen
2003-11-26 19:19 ` Philippe Troin
2003-11-27 1:32 ` Jens Petersen
2003-11-27 10:30 ` Jens Petersen
2003-11-30 5:43 ` Philippe Troin
2003-11-30 18:56 ` Danek Duvall
2003-12-01 2:36 ` Geoff Wing
2003-12-01 6:08 ` Philippe Troin
2003-12-01 6:56 ` Bart Schaefer
2003-12-01 8:32 ` Jens Petersen
2003-12-03 1:19 ` Philippe Troin
2003-12-09 4:50 ` Jens Petersen
2003-12-09 5:26 ` Philippe Troin
2003-12-01 1:06 ` Jens Petersen
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=m3d6bgq2tk.wl%petersen@redhat.com \
--to=petersen@redhat.com \
--cc=zsh-users@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).