From: Dan Nicolaescu <dann@ics.uci.edu>
To: "d.henman" <dhenman@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Failure in building Emacs 23.0.50 on Cygwin
Date: Sat, 01 Sep 2007 09:10:39 -0700 [thread overview]
Message-ID: <200709011610.l81GAdCe013060@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <20070901125313.1488@blackhawk> (d. henman's message of "Sat\, 01 Sep 2007 12\:53\:13 +0900")
"d.henman" <dhenman@gmail.com> writes:
> Dan Nicolaescu <dann@ics.uci.edu> wrote:
> > IMO the question should be asked the other way: how do you avoid
> > references to "croak".
> >
> > Adjust preprocessor code in dissociate_if_controlling_tty so that
> > croak is not used. Whether that is enough to make cygwin work, I don't
> > know.
>
> Here is the patch I came up with to avoid a reference to croak on the
> cygwin platform.
>
>
> --- term.c 2007-08-30 06:46:50.000000000 +0900
> +++ term.c.fixed 2007-09-01 10:39:51.906250000 +0900
> @@ -3142,8 +3142,10 @@
> emacs_close (fd);
> sigunblock (sigmask (SIGTTOU));
> #else
> +#ifndef CYGWIN
> /* Unknown system. */
> croak ();
> +#endif /* ! CYGWIN */
> #endif /* ! TIOCNOTTY */
> #endif /* ! USG */
> }
>
>
> Please review this and let me know if I can check it into cvs.
So In evect you are making dissociate_if_controlling_tty be an empty
function on cygwin. Is that the right thing to do for this platform?
If it is, then I think it would be cleaner to change
#ifdef WINDOWSNT
to
#if defined(WINDOWSNT) || defined(CYGWIN)
(BTW, does emacs work on cygwin after your patch?)
next prev parent reply other threads:[~2007-09-01 16:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 23:51 Failure in building Emacs 23.0.50 on Cygwin Angelo Graziosi
2007-08-30 0:56 ` Dan Nicolaescu
2007-08-30 23:42 ` Angelo Graziosi
2007-09-01 0:19 ` d.henman
2007-09-01 0:35 ` Dan Nicolaescu
2007-09-01 3:53 ` d.henman
2007-09-01 8:18 ` Eli Zaretskii
2007-09-01 10:14 ` d.henman
2007-09-01 10:36 ` Eli Zaretskii
2007-09-01 16:10 ` Dan Nicolaescu [this message]
2007-09-01 8:09 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200709011610.l81GAdCe013060@oogie-boogie.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=dhenman@gmail.com \
--cc=emacs-devel@gnu.org \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).