unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: trunk r115773: Port xcrun configuration to GNU/Linux.
Date: Sun, 29 Dec 2013 14:21:14 +0100	[thread overview]
Message-ID: <D6966EE9-1CF8-4ED1-8F05-A30FB5922A23@swipnet.se> (raw)
In-Reply-To: <wltxdshy1u.wl%mituharu@math.s.chiba-u.ac.jp>

Hello.

29 dec 2013 kl. 09:16 skrev YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>:

>>>>>> On Sat, 28 Dec 2013 23:51:47 -0800, Paul Eggert <eggert@cs.ucla.edu> said:
> 
>> YAMAMOTO Mitsuharu wrote:
>>> you cannot put quotes in the value of CPPFLAGS.
> 
>> Ah, OK, thanks, I reverted the change.
> 
>> If someone ever has spaces in xcsdkdir's value they can worry about
>> fixing this.
> 

Too bad autoconf is so bad at space handling.

> Yes.  Actually it is not so uncommon to have spaces as a part of a
> volume name (e.g., /Volumes/Macintosh HD/Applications/Xcode.app/...).
> That's why I didn't apply the patch in
> http://lists.gnu.org/archive/html/emacs-devel/2013-10/msg00760.html to
> the Mac port.
> 

We only need to use xcsdkdir if xcrun is used, I made that change.

> I'd encourage those who build Emacs themselves to install the Command
> Line Developer Tools on Mavericks (i.e., $ xcode-select --install) so
> they have /usr/include directory, which does not exist by default.

Last I checked, that required an additional registration.  Some people are not comfortable with that.
Also, upgrading Xcode is easier if xcrun is used.

	Jan D.




  parent reply	other threads:[~2013-12-29 13:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1VwcrN-0000fE-T1@vcs.savannah.gnu.org>
2013-12-27 23:50 ` trunk r115773: Port xcrun configuration to GNU/Linux Glenn Morris
2013-12-28  0:42   ` Paul Eggert
2013-12-28 10:13     ` Jan Djärv
2013-12-29  3:54     ` YAMAMOTO Mitsuharu
2013-12-29  7:16       ` Paul Eggert
2013-12-29  7:33         ` YAMAMOTO Mitsuharu
2013-12-29  7:51           ` Paul Eggert
2013-12-29  8:16             ` YAMAMOTO Mitsuharu
2013-12-29  9:11               ` Thien-Thi Nguyen
2013-12-29 10:44                 ` chad
2013-12-29 11:57                   ` YAMAMOTO Mitsuharu
2013-12-29 15:49                 ` Eli Zaretskii
2013-12-29 18:41                   ` Jan Djärv
2013-12-29 19:01                     ` Eli Zaretskii
2013-12-29 21:04                       ` Jan Djärv
2013-12-29 21:16                         ` Eli Zaretskii
2013-12-30 12:08                           ` Jan Djärv
2013-12-29 13:21               ` Jan Djärv [this message]
2013-12-29 13:55                 ` YAMAMOTO Mitsuharu
2013-12-29 16:28                   ` Jan Djärv
2013-12-29 19:14                     ` Jan Djärv
2013-12-28  9:54   ` Jan Djärv

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=D6966EE9-1CF8-4ED1-8F05-A30FB5922A23@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /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).