From: Philippe Troin <phil@fifi.org>
To: Danek Duvall <duvall@emufarm.org>
Cc: Jens Petersen <petersen@redhat.com>, Zsh-users <zsh-users@sunsite.dk>
Subject: Re: problem building zsh in background
Date: 30 Nov 2003 22:08:18 -0800 [thread overview]
Message-ID: <87fzg5ax4d.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <20031130185652.GA26891@lorien.emufarm.org>
Danek Duvall <duvall@emufarm.org> writes:
> On Sat, Nov 29, 2003 at 09:43:50PM -0800, Philippe Troin wrote:
>
> > Why do you want to run configure with nohup?
>
> In my case, it's more likely that I'd want to run configure from a cron
> script -- nightly builds.
>
> > I guess I could run the test in a separate, created pty, but that is
> > going to be messy to do portably in configure.
>
> Maybe a configure flag that forces tcsetpgrp() to be recognized as
> working, and skip the test? I know that it works properly on my
> platform, so I could use the flag and not worry about whether the build
> will hang or abort because of the test ...
Okay, what about the following behavior:
- keep the second patch (will fail if ran from cron or any other
situation where there is no ctty)
- add a --with-working-tcsetpgrp / --without-working-tcsetpgrp switch
to force configure to skip the test (instead of failing) and assume
a working / non-working tcsetpgrp
Would that satisfy everyone?
Phil.
next prev parent reply other threads:[~2003-12-01 6:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 8:17 Jens Petersen
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 [this message]
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=87fzg5ax4d.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=duvall@emufarm.org \
--cc=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).