unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Angelo Graziosi <angelo.g0@libero.it>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Failure building Emacs on WSL
Date: Thu, 1 Feb 2018 13:23:35 -0800	[thread overview]
Message-ID: <84d8aa8b-b7f1-ccdc-7e76-83cb502ef1a4@cs.ucla.edu> (raw)
In-Reply-To: <1510688534.63184.1517518773175@mail.libero.it>

On 02/01/2018 12:59 PM, Angelo Graziosi wrote:
> When is 'makeinfo' used building Emacs?
>
> If I build with
>
>    ./configure..
>    ./make...
>    ./make install
>
> is it really used?

It's not used if you're building from an Emacs distribution tarball, 
which is intended to be portable even to platforms lacking many 
developer tools. It is used if you're building from Git, where it's 
assumed you have a development environment with the appropriate tools, 
one of them being GNU texinfo.

It's probably best for you to arrange for your preferred environment to 
have all these tools. If that's not possible for some reason, you can 
first use GNU/Linux to create a tarball, and then copy the tarball to 
your more-limited development environment and build from that.




  reply	other threads:[~2018-02-01 21:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 15:38 Failure building Emacs on WSL Angelo Graziosi
2018-02-01 16:29 ` Eli Zaretskii
2018-02-01 16:46   ` Angelo Graziosi
2018-02-01 16:50     ` Noam Postavsky
2018-02-01 17:24     ` Eli Zaretskii
2018-02-01 20:59       ` Angelo Graziosi
2018-02-01 21:23         ` Paul Eggert [this message]
2018-02-02  8:30         ` Eli Zaretskii
2018-02-02 16:17           ` Angelo Graziosi
2018-02-01 19:09     ` Fabrice Popineau
2018-02-01 20:52       ` Angelo Graziosi

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=84d8aa8b-b7f1-ccdc-7e76-83cb502ef1a4@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=angelo.g0@libero.it \
    --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).