From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: PATH_SEPARATOR in test/automated/Makefile.in
Date: Wed, 27 Nov 2013 13:42:55 -0500 [thread overview]
Message-ID: <yxli09ofdc.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <834n6xae5e.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 27 Nov 2013 20:33:01 +0200")
Eli Zaretskii wrote:
> The problem is that (a) @PATH_SEPARATOR@ is replaced with ':' (of
> course: what else did you think MSYS Bash will use?),
You greatly overestimate my knowledge of and interest in MSYS Bash. ;)
> and (b) the automatic replacement of ":." with ";." doesn't happen
> either, because evidently the MSYS heuristics doesn't consider "."
> something that cannot be anything but a file name, so it plays safe
> and leaves it alone (":./" does work).
OK, err, ok. AFAIK, I just did what you told me to in
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15933#14
and subsequent. How come
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15933#47
said it worked then? (Ah, he uses an out-of-tree build, so his $srcdir
contains a "/".)
> So the possibilities as I see them are:
>
> . Remove PATH_SEPARATOR and use -L "$(PATH_SEPARATOR)$(srcdir)/"
> (with a slash) instead of -L "$(PATH_SEPARATOR)$(srcdir)"
Seems a bit flaky to me.
> . Leave PATH_SEPARATOR, but set it to ';' "manually" for MinGW,
> instead of relying on $PATH_SEPARATOR computed in configure by
> asking Bash.
Sounds better to me (assuming you mean making up some new variable,
rather than modifiying PATH_SEPARATOR, in case that inadvertently breaks
something else that's using it).
But please do whatever you think is best. Obviously I keep getting it
wrong.
next prev parent reply other threads:[~2013-11-27 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 18:33 PATH_SEPARATOR in test/automated/Makefile.in Eli Zaretskii
2013-11-27 18:42 ` Glenn Morris [this message]
2013-11-28 17:43 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yxli09ofdc.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.