From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: trunk r115773: Port xcrun configuration to GNU/Linux.
Date: Sun, 29 Dec 2013 10:11:16 +0100 [thread overview]
Message-ID: <87ppog2f9n.fsf@zigzag.favinet> (raw)
In-Reply-To: <wltxdshy1u.wl%mituharu@math.s.chiba-u.ac.jp> (YAMAMOTO Mitsuharu's message of "Sun, 29 Dec 2013 17:16:29 +0900")
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
() YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
() Sun, 29 Dec 2013 17:16:29 +0900
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/...).
How about making a symlink (w/o space!) from the builddir and adding
that to ‘CPPFLAGS’? Something like:
ln -f -s "$xcsdkdir" fake-xcsdkdir
xcsdkdir=`pwd`/fake-xcsdkdir
AS_VAR_APPEND([CPPFLAGS],[ -I$xcsdkdir/usr/include/libxml2])
The kludge can be conditionalized on space-detection, i suppose.
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2013-12-29 9:11 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 [this message]
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
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=87ppog2f9n.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=emacs-devel@gnu.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).