From: Glenn Morris <rgm@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 16772@debbugs.gnu.org, Juanma Barranquero <lekktu@gmail.com>
Subject: bug#16772: Failure in "make install" on MS-Windows
Date: Mon, 17 Feb 2014 14:06:53 -0500 [thread overview]
Message-ID: <dbsirhr22a.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAH8Pv0hD5h9vR=GRuXNcx8sOeuxbjh4aw=gYVSW5mx5oQf--VQ@mail.gmail.com> (Dani Moncayo's message of "Mon, 17 Feb 2014 19:57:02 +0100")
Dani Moncayo wrote:
> If you want the installation tree to go to a place that is
> different from the one specified by --prefix, say
>
> make install prefix=/where/ever/you/want
Seems weird to me for Emacs to be recommending that.
Why would one not specify the right prefix at configure time...?
>> And if you try, it will say:
>>
>> configure: error: expected an absolute directory name for --prefix:
>> ../myinstalldir
>
> No, it says something different: I've just tried this
[...]
> make install prefix=/c/tmp/dir2 GZIP_INFO= GZIP_PROG=
We seem to be having a failure to communicate.
"I ran make install with an absolute prefix" has no relevance to
"Here's what happens if you run configure with a relative prefix"
> And then I've applied the patch sent by Juanma, and tried again. This
> time the installation seems to be successful, and I see the file
> "<my-install-dir>/share/emacs/24.3.50/README.W32", as expected.
Hooray.
next prev parent reply other threads:[~2014-02-17 19:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH8Pv0gUZKzBjPePfpoRhYLwABObwyM_trfdTS-zRvTM0nw9MQ@mail.gmail.com>
2014-02-16 21:40 ` bug#16772: Failure in "make install" on MS-Windows Juanma Barranquero
2014-02-17 2:20 ` Glenn Morris
2014-02-17 2:41 ` Juanma Barranquero
2014-02-17 11:42 ` Dani Moncayo
2014-02-17 12:38 ` Juanma Barranquero
2014-02-17 14:49 ` Eli Zaretskii
2014-02-17 14:54 ` Juanma Barranquero
2014-02-17 15:06 ` Dani Moncayo
2014-02-17 14:48 ` Eli Zaretskii
2014-02-17 15:06 ` Dani Moncayo
2014-02-17 15:18 ` Juanma Barranquero
2014-02-17 15:29 ` Dani Moncayo
2014-02-17 15:39 ` Juanma Barranquero
2014-02-17 15:58 ` Eli Zaretskii
2014-02-17 16:06 ` Juanma Barranquero
2014-02-17 15:31 ` Eli Zaretskii
2014-02-17 15:33 ` Dani Moncayo
2014-02-17 15:58 ` Eli Zaretskii
2014-02-17 16:16 ` Dani Moncayo
2014-02-17 16:44 ` Eli Zaretskii
2014-02-17 18:00 ` Glenn Morris
2014-02-17 18:57 ` Dani Moncayo
2014-02-17 19:01 ` Dani Moncayo
2014-02-17 19:05 ` Juanma Barranquero
2014-02-17 19:09 ` Dani Moncayo
2014-02-17 21:21 ` Juanma Barranquero
2014-02-17 19:06 ` Glenn Morris [this message]
2014-02-17 20:36 ` Eli Zaretskii
2014-02-17 18:58 ` Eli Zaretskii
2014-02-17 19:01 ` Glenn Morris
2014-02-17 19:13 ` Glenn Morris
2014-02-17 4:54 ` Eli Zaretskii
2014-02-17 11:42 ` Dani Moncayo
2014-02-17 12:32 ` Juanma Barranquero
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=dbsirhr22a.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=16772@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
--cc=lekktu@gmail.com \
/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).