unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: trunk r115773: Port xcrun configuration to GNU/Linux.
Date: Mon, 30 Dec 2013 13:08:56 +0100	[thread overview]
Message-ID: <E7099748-1FA9-4983-91F2-BC628C9DD287@swipnet.se> (raw)
In-Reply-To: <83wqin1hod.fsf@gnu.org>

Hello.

29 dec 2013 kl. 22:16 skrev Eli Zaretskii <eliz@gnu.org>:

>> From: Jan Djärv <jan.h.d@swipnet.se>
>> Date: Sun, 29 Dec 2013 22:04:02 +0100
>> Cc: emacs-devel <emacs-devel@gnu.org>
>> 
>> Hello.
>> 
>> 29 dec 2013 kl. 20:01 skrev Eli Zaretskii <eliz@gnu.org>:
>> 
>>>> From: Jan Djärv <jan.h.d@swipnet.se>
>>>> Date: Sun, 29 Dec 2013 19:41:28 +0100
>>>> Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
>>>> 
>>>> This has nothing to do with builddir, but include directories passed to the compiler with -I.  As this has to do with the configure code and how it handles spaces, I'm pretty sure this fails everywhere. 
>>> 
>>> The solution might be to use relative file names.
>> 
>> It would not help here, the trees are urelated.
>> I.e. the relative path would also have a space in it, something like:
>> 
>> ../../../../Volumes/Macintosh HD/...
> 
> How about stuffing the file name into an environment variable, and
> using that in configure?

Good try, but no.  I think this is impossible without modifying configure variables, i.e. ac_compile.

ac_compile is:

  ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'

As said, it is used like this:

  (eval "$ac_compile") 2>conftest.err

Eval first expands the variables, and then word splits on whitespace, regardless of quoting characters.
So there is no way to put something in CPPFLAGS with a whitespace that eval wont word-split on that whitespace.
This is a fundamental limitation in autoconf.

I'm happy to be proven wrong, but I can't see any way to do it, except modifying ac_compile.

	Jan D.




  reply	other threads:[~2013-12-30 12:08 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 [this message]
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=E7099748-1FA9-4983-91F2-BC628C9DD287@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=eliz@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).