From: ashish.is@lostca.se (Ashish SHUKLA)
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 15129@debbugs.gnu.org
Subject: bug#15129: Emacs broken on FreeBSD in/after r113315
Date: Wed, 21 Aug 2013 14:19:19 +0530 [thread overview]
Message-ID: <86bo4rwhrk.fsf@chateau.d.if> (raw)
In-Reply-To: <52145B45.4010806@cs.ucla.edu> (Paul Eggert's message of "Tue, 20 Aug 2013 23:16:37 -0700")
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
On Tue, 20 Aug 2013 23:16:37 -0700, Paul Eggert <eggert@cs.ucla.edu> said:
> I looked into this a bit more.
> As I understand it, FreeBSD 8 posix_openpt supports O_CLOEXEC
> but this is undocumented, FreeBSD 9 posix_openpt rejects
> attempts to use O_CLOEXEC, and future FreeBSD posix_openpt
> will support O_CLOEXEC again. See:
> http://lists.freebsd.org/pipermail/freebsd-bugs/2011-November/046295.html
> http://bogomips.org/ruby.git/patch/?id=452bf3b9c954d770ccb704cb9f5470f515e00584
> What a mess, huh? I installed two patches as trunk
> bzr 113963 and 113964 to try to work around FreeBSD's
> flip-flopping on this issue. Please let us know if they
> fix your problem.
Hi,
I tried r113965, and your commits seems to fix the issue for me. I've asked
Christoph (the reporter of Debian kFreeBSD) to also test it.
Thanks!
--
Ashish SHUKLA
“Digital files cannot be made uncopyable, any more than water can be made not
wet.” (Bruce Schneier, 2001-05-15)
Sent from my Emacs
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2013-08-21 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 6:29 bug#15129: 24.3.50; Emacs broken on FreeBSD in/after r113315 Ashish SHUKLA
2013-08-19 6:36 ` Glenn Morris
2013-08-19 6:46 ` Ashish SHUKLA
2013-08-19 7:36 ` Ashish SHUKLA
2013-08-20 17:26 ` Glenn Morris
2013-08-19 7:52 ` Paul Eggert
2013-08-21 6:16 ` bug#15129: " Paul Eggert
2013-08-21 8:49 ` Ashish SHUKLA [this message]
2013-08-21 15:20 ` Paul Eggert
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=86bo4rwhrk.fsf@chateau.d.if \
--to=ashish.is@lostca.se \
--cc=15129@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).