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:34:51 +0300 [thread overview]
Message-ID: <83bmzm4v50.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58ojeV_83pVATxMM9mgmei168DpV7NWiPevdsJLCfdwWh_g@mail.gmail.com> (message from Richard Copley on Sat, 17 Sep 2016 12:28:02 +0100)
> From: Richard Copley <rcopley@gmail.com>
> Date: Sat, 17 Sep 2016 12:28:02 +0100
> Cc: Paul Eggert <eggert@cs.ucla.edu>, Bob Halley <halley@play-bow.org>,
> Emacs Development <emacs-devel@gnu.org>
>
> >> The Windows build is broken too (with MSYS2), presumably for a similar
> >> reason.
> >
> > It isn't broken here. Can you show the error messages?
>
> Sure, give me a few minutes. Did you reconfigure? You need the
> generated limits.h.
The configure script runs automatically when you say "make" in the
top-level directory. And yes, limit.h was recreated.
I just re-run autogen.sh and the configure script, to make sure -- no
errors in sight.
What GCC version do you have?
next prev parent reply other threads:[~2016-09-17 11:34 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bmzm4v50.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 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.