From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Malcolm Purvis <malcolmp@xemacs.org>
Cc: ding@gnus.org
Subject: Re: 'configure' doesn't preserve spaces in directory path.
Date: Fri, 08 Feb 2008 08:44:00 +0900 [thread overview]
Message-ID: <b4msl049vsv.fsf@jpl.org> (raw)
In-Reply-To: <b4mtzkofeep.fsf@jpl.org>
>>>>> Katsumi Yamaoka wrote:
>>>>>> Malcolm Purvis wrote:
>> Back in 2006, Chris Shenton reported a bug in configure when the
>> installation path contains a space:
>> http://article.gmane.org/gmane.emacs.gnus.general/62483
>> In response Katsumi Yamaoka posted an improved patch:
>> http://article.gmane.org/gmane.emacs.gnus.general/62487
>> For some reason this patch hasn't been applied, but the bug is still
>> present, and bit me recently. Would it be possible to have this patch
>> applied?
>> Katsumi Yamaoka's patch is:
> I realized that that was totally insufficient to solve the problem.
> Could you try the attached patch and the configure script?
I arranged the patch neatly and installed in the Gnus CVS trunk.
Note that the configure script there has been regenerated by
autoconf v2.61[1], and the file timestamp should be newer than
configure.in and aclocal.m4 (actually, I installed the other
files first, and then installed the configure script after a
while). However, if it doesn't go well when you check it out,
it will be regenerated using the version of autoconf available
in your system, or it might not work if you don't have autoconf
installed. If you meet such a trouble, please let me know.
[1] Autoconf v2.60 and the greater ones support the installation
directory name containing spaces and/or tabs.
next prev parent reply other threads:[~2008-02-07 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 12:14 Malcolm Purvis
2008-02-05 0:14 ` Katsumi Yamaoka
2008-02-07 23:44 ` Katsumi Yamaoka [this message]
2008-02-08 11:45 ` Malcolm Purvis
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=b4msl049vsv.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=malcolmp@xemacs.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.
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 NNTP newsgroup(s).