unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Copley <rcopley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Bob Halley <halley@play-bow.org>,
	Paul Eggert <eggert@cs.ucla.edu>,
	Emacs Development <emacs-devel@gnu.org>
Subject: Re: unexmacosx.c and limits.h problem
Date: Sat, 17 Sep 2016 13:46:47 +0100	[thread overview]
Message-ID: <CAPM58ohsyD5AcWNJ7k4FEpgUg7npF_upEh0eH=M9too9MYiH5w@mail.gmail.com> (raw)
In-Reply-To: <834m5e4s1b.fsf@gnu.org>

On 17 September 2016 at 13:41, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Richard Copley <rcopley@gmail.com>
>> Date: Sat, 17 Sep 2016 13:28:05 +0100
>> Cc: Paul Eggert <eggert@cs.ucla.edu>, Bob Halley <halley@play-bow.org>,
>>       Emacs Development <emacs-devel@gnu.org>
>>
>> My preprocessed file doesn't show the #include or #define directives.
>> It sounds like yours does. Apparently another difference between our
>> toolchains. I obtained the preprocessed file the same way you did.
>
> No, there's no difference.  The inclusion evidence is like this:
>
>   # 1 "../lib/limits.h" 1 3
>
> Do you see such a line in the preprocessed file?

Yes.

> If you do, then does
> it include this line further down:
>
>   #define LLONG_WIDTH _GL_INTEGER_WIDTH (LLONG_MIN, LLONG_MAX)

No.

> I then searched back for _GNU_SOURCE and saw this:
>
>   #define _GNU_SOURCE 1
>
> and a little ways above it I saw this:
>
>   # 1583 "./config.h"
>
> Do you see these?
>
> Etc. etc. -- just go back and look whether the file inclusion I
> described happens on your system.
>
>> I suppose the preprocessed source is no use to you, since you don't
>> have the same headers unless you update your MSYS, and if you do that
>> you won't need anything from me.
>
> If you cannot figure this out, send the preprocessed source of
> w32proc.c, sure.  I will take a look.
>
> Thanks.

Thanks for that. I might have found the difference that makes the
difference. Please see my other message.



  reply	other threads:[~2016-09-17 12:46 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 [this message]
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='CAPM58ohsyD5AcWNJ7k4FEpgUg7npF_upEh0eH=M9too9MYiH5w@mail.gmail.com' \
    --to=rcopley@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=halley@play-bow.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 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).