From: Keith David Bershatsky <esq@lawlist.com>
To: Emacs Devel <emacs-devel@gnu.org>
Subject: w32 port: SVG Path Commands' has no Up field (perhaps incorrect sectioning?).
Date: Mon, 15 Jul 2019 13:53:54 -0700 [thread overview]
Message-ID: <m2pnmbf28t.wl%esq@lawlist.com> (raw)
When building master branch from today (0797b39185e66983c7286e89f93dd4f6c83b6ea7) on Windows 32 (minGW and ezwinports downloaded a few years ago) with the following build options:
CFLAGS='-O0 -g3' ./configure \
--prefix=/c/docume~1/admini~1/desktop/trunk \
--enable-checking='yes,glyphs' \
--enable-check-lisp-object-type \
--without-compress-install \
--without-makeinfo \
--with-gnutls=no \
--with-mailutils \
--without-makeinfo
... the build stops with the following output:
make[1]: Leaving directory `/c/docume~1/admini~1/desktop/emacs/lisp'
make info-real info-dir
make[1]: Entering directory `/c/docume~1/admini~1/desktop/emacs'
make -C doc/lispref info
make[2]: Entering directory `/c/docume~1/admini~1/desktop/emacs/doc/lispref'
/c/mingw/bin/mkdir -p ../../info
GEN ../../info/elisp.info
/c/docume~1/admini~1/desktop/emacs/doc/lispref//display.texi:5740: `SVG Path Commands' has no Up field (perhaps incorrect sectioning?).
make[2]: *** [../../info/elisp.info] Error 1
make[2]: Leaving directory `/c/docume~1/admini~1/desktop/emacs/doc/lispref'
make[1]: *** [lispref-info] Error 2
make[1]: Leaving directory `/c/docume~1/admini~1/desktop/emacs'
make: *** [info] Error 2
next reply other threads:[~2019-07-15 20:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 20:53 Keith David Bershatsky [this message]
2019-07-16 1:20 ` w32 port: SVG Path Commands' has no Up field (perhaps incorrect sectioning?) Noam Postavsky
2019-07-18 8:38 ` Eli Zaretskii
2019-07-18 9:31 ` Robert Pluim
-- strict thread matches above, loose matches on Subject: below --
2019-07-16 3:06 Keith David Bershatsky
2019-07-16 14:05 ` Noam Postavsky
2019-07-18 17:07 Keith David Bershatsky
2019-07-18 17:12 ` 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=m2pnmbf28t.wl%esq@lawlist.com \
--to=esq@lawlist.com \
--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.