From: Noam Postavsky <npostavs@gmail.com>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: w32 port: SVG Path Commands' has no Up field (perhaps incorrect sectioning?).
Date: Tue, 16 Jul 2019 10:05:48 -0400 [thread overview]
Message-ID: <CAM-tV-9B7NcnuVp+C+KR2wMM1T7-bG-uHU+kZkCzF1sr=LKahQ@mail.gmail.com> (raw)
In-Reply-To: <m2zhlebruu.wl%esq@lawlist.com>
On Mon, 15 Jul 2019 at 23:06, Keith David Bershatsky <esq@lawlist.com> wrote:
> Because I have been able to successfully build Emacs for several years using this same Windows XP SP3 virtual machine with an outdated timestamp, I believe that it may only be a contributing factor to the error in this thread, rather than the root cause. I can certainly update the timestamp on the virtual machine and build Emacs a third time today using 0797b39185e66983c7286e89f93dd4f6c83b6ea7, but I would guess that I will have the same result in a failed build.
By outdated timestamps, I meant the modification times of your source
and/or build files (e.g., maybe the VM's clock got out of sync at some
point?). But looking at your build log again, it's something even
stranger than that:
GEN globals.h
CC emacs.o
gcc -std=gnu11 emacs.o -o emacs
Where is that last line coming from? It's trying to produce the
'emacs' executable without linking any of the object files except
emacs.o. And it didn't use the silent rule format (CCLD).
next prev parent reply other threads:[~2019-07-16 14:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 3:06 w32 port: SVG Path Commands' has no Up field (perhaps incorrect sectioning?) Keith David Bershatsky
2019-07-16 14:05 ` Noam Postavsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-18 17:07 Keith David Bershatsky
2019-07-18 17:12 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM-tV-9B7NcnuVp+C+KR2wMM1T7-bG-uHU+kZkCzF1sr=LKahQ@mail.gmail.com' \
--to=npostavs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=esq@lawlist.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 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.