all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14821@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#14821: Build broken on 64-bit Cygwin starting with bzr revision 113315
Date: Tue, 09 Jul 2013 13:13:26 -0400	[thread overview]
Message-ID: <51DC44B6.7040507@cornell.edu> (raw)
In-Reply-To: <831u77wtkz.fsf@gnu.org>

On 7/9/2013 1:07 PM, Eli Zaretskii wrote:
>> Date: Tue, 09 Jul 2013 12:46:44 -0400
>> From: Ken Brown <kbrown@cornell.edu>
>> CC: 14821@debbugs.gnu.org, eggert@cs.ucla.edu
>>
>> the symbol 'setmode' is no longer exported in 64bit Cygwin.
>
> Are you saying that there's no way of reading files in text mode while
> removing CR characters from CR-LF pairs?
>
>> That's
>> what caused the build failure.  And the code in pipe2.c that calls
>> setmode should never actually get executed on Cygwin anyway because of this:
>>
>>           int result = pipe2 (fd, flags);
>>           if (!(result < 0 && errno == ENOSYS))
>>             {
>>               have_pipe2_really = 1;
>>               return result;
>
> So define setmode away for Cygwin versions that don't have it.  Not
> everyone runs the bleeding edge.

The discussion is moot now.  Paul just submitted a patch to Gnulib that 
should fix it in a better way than what I suggested.

Ken






  reply	other threads:[~2013-07-09 17:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 15:47 bug#14821: Build broken on 64-bit Cygwin starting with bzr revision 113315 Ken Brown
2013-07-09 12:33 ` Ken Brown
2013-07-09 13:28   ` Ken Brown
2013-07-09 16:17   ` Eli Zaretskii
2013-07-09 16:46     ` Ken Brown
2013-07-09 17:07       ` Eli Zaretskii
2013-07-09 17:13         ` Ken Brown [this message]
2013-07-09 17:29           ` Paul Eggert
2013-07-09 19:52             ` Ken Brown

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=51DC44B6.7040507@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=14821@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.