unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: halley@play-bow.org, eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: unexmacosx.c and limits.h problem
Date: Sat, 17 Sep 2016 14:18:48 +0300	[thread overview]
Message-ID: <83d1k24vvr.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58oi=TS8FEtsuUZC2GXeeti=DaS7O0wZaCsHLGs+6XusqgQ@mail.gmail.com> (message from Richard Copley on Sat, 17 Sep 2016 12:03:14 +0100)

> From: Richard Copley <rcopley@gmail.com>
> Date: Sat, 17 Sep 2016 12:03:14 +0100
> Cc: Bob Halley <halley@play-bow.org>, Emacs Development <emacs-devel@gnu.org>
> 
> On 17 September 2016 at 02:02, Paul Eggert <eggert@cs.ucla.edu> wrote:
> > On 09/16/2016 04:04 PM, Bob Halley wrote:
> >>
> >> +#ifndef _GNU_SOURCE
> >> +#define _GNU_SOURCE 1
> >> +#endif
> >
> >
> > Thanks, I installed that into Emacs master.
> 
> The Windows build is broken too (with MSYS2), presumably for a similar
> reason.

It isn't broken here.  Can you show the error messages?



  reply	other threads:[~2016-09-17 11:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16 23:04 unexmacosx.c and limits.h problem Bob Halley
2016-09-17  1:02 ` Paul Eggert
2016-09-17 11:03   ` Richard Copley
2016-09-17 11:18     ` Eli Zaretskii [this message]
2016-09-17 11:28       ` Richard Copley
2016-09-17 11:31         ` Richard Copley
2016-09-17 11:51           ` Eli Zaretskii
2016-09-17 12:28             ` Richard Copley
2016-09-17 12:40               ` Richard Copley
2016-09-17 12:56                 ` Richard Copley
2016-09-17 13:38                   ` Eli Zaretskii
2016-09-17 18:14                     ` Paul Eggert
2016-09-17 12:41               ` Eli Zaretskii
2016-09-17 12:46                 ` Richard Copley
2016-09-17 11:34         ` Eli Zaretskii
2016-09-17 11:38           ` Richard Copley

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=83d1k24vvr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=halley@play-bow.org \
    --cc=rcopley@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 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).