From: Angelo Graziosi <angelo.g0@libero.it>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Failure building Emacs on WSL
Date: Fri, 2 Feb 2018 17:17:28 +0100 (CET) [thread overview]
Message-ID: <2015487793.137269.1517588249042@mail.libero.it> (raw)
In-Reply-To: <838tcbequ6.fsf@gnu.org>
> Il 2 febbraio 2018 alle 9.30 Eli Zaretskii ha scritto:
>
> When the build process detects that your Info manuals (in info/) are
> out of sync with their Texinfo sources (under doc/*/).
Thanks for claryfication...
> Is the Cygwin Texinfo installation really so heavy-weight? Is it not
> possible to install only Texinfo, without TeX? If you don't have TeX,
> you will be unable to produce the printed versions of the manuals
> (PDF, DVI, PS formats), but if you never need that, TeX is just (a lot
> of) ballast. So in that case, just installing Texinfo alone, which is
> a relatively small package, will allow you to build the manuals when
> you build Emacs from Git, and get the latest manuals to go with the
> binaries you built.
MSYS2 has not texlive packages so its texinfo package install only makeinfo and some other utility but WSL (the Windows Subsystem for Linux in W10) wants to install also some texlive package when one installs texinfo...
The issue was originated by the fact that I removed C:\msys64\usr\bin from Windows PATH so in the previous builds the WSL build of Emacs was really using the MSYS2 makeinfo.
Thanks,
Angelo.
next prev parent reply other threads:[~2018-02-02 16:17 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
2018-02-02 8:30 ` Eli Zaretskii
2018-02-02 16:17 ` Angelo Graziosi [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2015487793.137269.1517588249042@mail.libero.it \
--to=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 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.