all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org, somasis@exherbo.org, somasissounds@gmail.com
Subject: Re: [PATCH] src/print.c: Check for __GLIBC__ rather than GNU_LINUX
Date: Fri, 01 Apr 2016 09:43:19 +0300	[thread overview]
Message-ID: <83shz5u8vs.fsf@gnu.org> (raw)
In-Reply-To: <56FD8A8B.3040808@cs.ucla.edu> (message from Paul Eggert on Thu,  31 Mar 2016 13:37:31 -0700)

> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Thu, 31 Mar 2016 13:37:31 -0700
> Cc: Kylie McClain <somasis@exherbo.org>
> 
> I haven't installed it into 'master' yet, to give Eli a heads-up about 
> the impending change.

Thanks.  I needed the additional patch below to get the patch to
compile (how do other ports get F_DUPFD_CLOEXEC?).

After that, temacs seems to hang during loadup.  Looks like it hangs
inside the libc function 'close'.  I don't have enough free time now
to do anything serious on master.  Hopefully, someone else will be
able to look into this, find out why it hangs, and suggest a remedy.


--- src/print.c~0	2016-04-01 09:32:53.060500000 +0300
+++ src/print.c	2016-04-01 09:36:24.591750000 +0300
@@ -38,6 +38,10 @@ along with GNU Emacs.  If not, see <http
 #include <float.h>
 #include <ftoastr.h>
 
+#ifdef WINDOWSNT
+#include <sys/socket.h>		/* for F_DUPFD_CLOEXEC */
+#endif
+
 struct terminal;
 
 /* Avoid actual stack overflow in print.  */



  parent reply	other threads:[~2016-04-01  6:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30  5:22 [PATCH] src/print.c: Check for __GLIBC__ rather than GNU_LINUX Kylie McClain
2016-03-31 20:37 ` Paul Eggert
2016-03-31 21:26   ` Kylie McClain
2016-04-01  6:43   ` Eli Zaretskii [this message]
2016-04-01  7:46     ` Paul Eggert
2016-04-02  8:35       ` Eli Zaretskii
2016-04-03  8:24         ` Paul Eggert
2016-04-04 16:45         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83shz5u8vs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=somasis@exherbo.org \
    --cc=somasissounds@gmail.com \
    /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.