From: Eli Zaretskii <eliz@gnu.org>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: emacs-devel@gnu.org
Subject: Re: w32 master branch: "make[2]: *** [calendar/cal-loaddefs.el] Error 3"
Date: Thu, 04 Apr 2019 16:07:23 +0300 [thread overview]
Message-ID: <83o95ldilw.fsf@gnu.org> (raw)
In-Reply-To: <m2d0m2620p.wl%esq@lawlist.com> (message from Keith David Bershatsky on Wed, 03 Apr 2019 17:35:18 -0700)
> Date: Wed, 03 Apr 2019 17:35:18 -0700
> From: Keith David Bershatsky <esq@lawlist.com>
> Cc: emacs-devel@gnu.org
>
> I am still struggling, however, with building a patched version from 03/28/2019 (containing a proof concept of the multiple fake cursors feature). There is only one new lisp file (crosshairs.el), which has six (6) of these:
>
> ;;;###autoload
>
> For each loaddefs.el, I see a loop of what seems like somewhere between 50 and 100 repetitions until the build process moves on to the next loaddefs.el file; and, the loops look like this:
>
> c:/docume~1/admini~1/desktop/emacs/lisp/loaddefs.el and c:/Documents and Settings/Administrator/Desktop/emacs/lisp/loaddefs.el are the same file
They are just warnings.
> In the Console2 terminal using the MinGW_32 goodies, I do the following:
>
> cd /c/docume~1/admini~1/desktop/
I think this is the cause of your problem, right there: you are using
short 8+3 aliases of long file names. Why are you doing that? Just
say
cd "/c/Documents and Settings/Administrator/Desktop"
> CFLAGS='-O0 -g3' ./configure \
> --prefix=/c/docume~1/admini~1/desktop/trunk \
Likewise here: use the full long file names.
Alternatively, just ignore the warnings, they are harmless.
next prev parent reply other threads:[~2019-04-04 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 0:35 w32 master branch: "make[2]: *** [calendar/cal-loaddefs.el] Error 3" Keith David Bershatsky
2019-04-04 13:07 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-05 1:05 Keith David Bershatsky
2019-04-05 6:16 ` Eli Zaretskii
2019-04-03 18:59 Keith David Bershatsky
2019-04-03 19:21 ` 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
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=83o95ldilw.fsf@gnu.org \
--to=eliz@gnu.org \
--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 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).