all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Keith David Bershatsky <esq@lawlist.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: w32 master branch: "make[2]: *** [calendar/cal-loaddefs.el] Error 3"
Date: Wed, 03 Apr 2019 17:35:18 -0700	[thread overview]
Message-ID: <m2d0m2620p.wl%esq@lawlist.com> (raw)

Thank you, Eli, for letting me know that the w32 build succeeds on your end.

I was eventually able to build a clean w32 Emacs master branch from today (04/03/2019) -- without incident.

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

  ...

  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

  ...

  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


In the Console2 terminal using the MinGW_32 goodies, I do the following:

cd /c/docume~1/admini~1/desktop/

rm -rf emacs

git clone -b master git://git.sv.gnu.org/emacs.git

cd /c/docume~1/admini~1/desktop/emacs

git reset --hard 2da9f8bf4222fda504f43b4757e154999cdbbf2c

;;; "HEAD is now at 2da9f8b Fix display of sliced images on MS-Windows"

git apply /path/to/the/patch.diff

./autogen.sh

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

make

...

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

> Date: [04-03-2019 12:21:38] <03 Apr 2019 22:21:38 +0300>
> 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: Wed, 03 Apr 2019 11:59:07 -0700
> > From: Keith David Bershatsky <esq@lawlist.com>
> >
> > I am able to successfully build Emacs master branch 03/28/2019 on NS and X11, however, the w32 build fails (Windows XP SP-3, using MinGW-32 and the ezwinports goodies from a couple of years ago):
> >
> > This application has requested the Runtime to terminate it in an unusual way.
> > Please contact the application's support team for more information.
> > make[2]: *** [calendar/cal-loaddefs.el] Error 3
> > make[2]: Leaving directory `/c/docume~1/admini~1/desktop/emacs/lisp'
> > make[1]: *** [../lisp/loaddefs.el] Error 2
> > make[1]: Leaving directory `/c/docume~1/admini~1/desktop/emacs/src'
> > make: *** [src] Error 2
> 
> Doesn't happen here.  Is this a fresh checkout, or a directory where
> you already built Emacs in the past?  If the latter, there might be
> stale files around which cause this, so be sure to clean up the tree.



             reply	other threads:[~2019-04-04  0:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04  0:35 Keith David Bershatsky [this message]
2019-04-04 13:07 ` w32 master branch: "make[2]: *** [calendar/cal-loaddefs.el] Error 3" Eli Zaretskii
  -- 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2d0m2620p.wl%esq@lawlist.com \
    --to=esq@lawlist.com \
    --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.