unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 7859@debbugs.gnu.org, bug-gnulib <bug-gnulib@gnu.org>,
	7856@debbugs.gnu.org, emacs-devel@gnu.org
Subject: bug#7859: syncing Emacs from sources maintained elsewhere
Date: Wed, 19 Jan 2011 15:44:40 -0800	[thread overview]
Message-ID: <4D377768.8070504__46024.9700620354$1295481314$gmane$org@cs.ucla.edu> (raw)
In-Reply-To: <4D370928.1040601@swipnet.se>

I see that Jan Djärv tracked the problem down:
unexmacosx.c included <unistd.h> before <config.h>,
and this caused the problem.  Generally speaking, <config.h>
should be included before all other files, since it
defines macros such as _FILE_OFFSET_BITS that may affect
the ABI, and compiling files sometimes with one ABI and
sometimes with another can lead to disaster.

I see that unexmacos.c still doesn't include <config.h> first,
though.  I suggest that it be changed to do that.

A quick scan for other files with the problem show that
the following files probably need the "#include <config.h>"
moved to the top too:

  w32.c
  w32proc.c





  parent reply	other threads:[~2011-01-19 23:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D2BA939.5090903@cs.ucla.edu>
     [not found] ` <4D34A88F.4080400@cs.ucla.edu>
     [not found]   ` <vz1aaiyjzcq.fsf@gmail.com>
     [not found]     ` <E1PfDM1-0003kg-V2@fencepost.gnu.org>
     [not found]       ` <4D35D842.5030003@cs.ucla.edu>
     [not found]         ` <cksjwp7kq7.fsf@fencepost.gnu.org>
2011-01-19  6:04           ` bug#7856: syncing Emacs from sources maintained elsewhere Paul Eggert
2011-01-19  6:04           ` bug#7859: " Paul Eggert
     [not found]           ` <4D367F0B.3040808@cs.ucla.edu>
     [not found]             ` <4D368D16.7020702@swipnet.se>
     [not found]               ` <25y66hjmiu.fsf@fencepost.gnu.org>
2011-01-19 10:38                 ` Paul Eggert
2011-01-19 10:38                 ` bug#7856: " Paul Eggert
     [not found]                 ` <4D36BF43.3050007@cs.ucla.edu>
2011-01-19 15:54                   ` bug#7856: bug#7859: " Jan Djärv
2011-01-19 15:54                   ` Jan Djärv
     [not found]                   ` <4D370928.1040601@swipnet.se>
2011-01-19 23:44                     ` bug#7856: " Paul Eggert
2011-01-19 23:44                     ` Paul Eggert [this message]
     [not found]                     ` <4D377768.8070504@cs.ucla.edu>
2011-01-20  0:21                       ` Eli Zaretskii
2011-01-20  6:45                       ` bug#7856: " Jan Djärv
2011-01-20  6:45                       ` Jan Djärv
     [not found]                       ` <4D37D9FD.3050805@swipnet.se>
2011-01-20  7:51                         ` bug#7856: " Paul Eggert
2011-01-20  7:51                         ` Paul Eggert
     [not found]                         ` <4D37E970.2060803@cs.ucla.edu>
2011-01-20 11:26                           ` bug#7856: " Jan D.
2011-01-20 11:26                           ` Jan D.
2011-01-20  0:27                   ` bug#7856: " Eric Blake
2011-01-20  0:27                   ` bug#7859: " Eric Blake

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='4D377768.8070504__46024.9700620354$1295481314$gmane$org@cs.ucla.edu' \
    --to=eggert@cs.ucla.edu \
    --cc=7856@debbugs.gnu.org \
    --cc=7859@debbugs.gnu.org \
    --cc=bug-gnulib@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    /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).