From: Keith David Bershatsky <esq@lawlist.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Robert Pluim <rpluim@gmail.com>, emacs-devel@gnu.org
Subject: Re: w32 port: SVG Path Commands' has no Up field (perhaps incorrect sectioning?).
Date: Thu, 18 Jul 2019 10:07:53 -0700 [thread overview]
Message-ID: <m27e8fxod2.wl%esq@lawlist.com> (raw)
Given that the relevant commit has been reverted, I am assuming that Eli Z. does not need me to do anything further on this issue. If by chance anyone still needs something, just let me know.
Keith
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> Date: [07-18-2019 02:31:36] <18 Jul 2019 11:31:36 +0200>
> From: Robert Pluim <rpluim@gmail.com>
> To: Eli Zaretskii <eliz@gnu.org>
> Cc: Keith David Bershatsky <esq@lawlist.com>, emacs-devel@gnu.org
> Subject: Re: w32 port: SVG Path Commands' has no Up field (perhaps incorrect sectioning?).
>
> >>>>> On Thu, 18 Jul 2019 11:38:48 +0300, Eli Zaretskii <eliz@gnu.org> said:
> Eli> I see no "SVG Path Commands" in lispref/display.texi. Do you still
> Eli> see this problem with today's master?
>
> Lars reverted the relevant commits as the copyright paperwork isnʼt in
> order yet.
>
> Robert
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Date: [07-18-2019 01:38:48] <18 Jul 2019 11:38:48 +0300>
From: Eli Zaretskii <eliz@gnu.org>
> Date: Mon, 15 Jul 2019 13:53:54 -0700
> From: Keith David Bershatsky <esq@lawlist.com>
>
> 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?).
I see no "SVG Path Commands" in lispref/display.texi. Do you still
see this problem with today's master?
next reply other threads:[~2019-07-18 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 17:07 Keith David Bershatsky [this message]
2019-07-18 17:12 ` w32 port: SVG Path Commands' has no Up field (perhaps incorrect sectioning?) Eli Zaretskii
-- 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-15 20:53 Keith David Bershatsky
2019-07-16 1:20 ` Noam Postavsky
2019-07-18 8:38 ` Eli Zaretskii
2019-07-18 9:31 ` Robert Pluim
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=m27e8fxod2.wl%esq@lawlist.com \
--to=esq@lawlist.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@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).