unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org
Subject: Re: Build failure on Windows
Date: Tue, 07 Mar 2017 17:13:43 +0100	[thread overview]
Message-ID: <58BEDC37.7020405@gmx.at> (raw)
In-Reply-To: <83y3whgkga.fsf@gnu.org>

 >>     1. If you want to build Emacs outside of the source tree
 >>        (recommended), create the build directory and chdir there.
 >>
 >> Maybe we should remove that recommendation?
 >
 > I don't see why.  Your problems are all related to outdated Lisp
 > files, so out-of-tree builds are unlikely to be a factor.  (Which
 > means I again don't understand why you report a perceptible
 > degradation in build success rates, while I don't see anything close
 > to that.)

Was the gnulib.mk issue from my first message in this thread related to
out-of-tree building?

 >>   > Are the failures always with outdated Lisp files?  Or are they due to
 >>   > other aspects of the build?
 >>
 >> I had three typical groups of failures (some of them also on GNU/Linux
 >> IIRC):
 >>
 >> - The "require cl-lib" ones - by far the largest group and by far the
 >>     greatest annoyance.  Do we really need cl-lib in preloaded Elisp?  OK,
 >>     this ship sailed long ago ...
 >>
 >> - More specific cl-generic.el related errors.  IIRC usually something
 >>     about cl-defgeneric but I don't recall the precise text any more.
 >>     probably a subgroup of the first one.
 >>
 >> - Something I certainly never saw before about invalid bytecode.
 >
 > These are all related to outdated *.elc files.

OK.  I never saw these in the past years.  Maybe I was just lucky.

 >> Also, failures occurred only when a configure step was performed before
 >> (which is probably obvious).  Pure makes never failed.
 >
 > You mean, when configure is run automatically by "make"?

Yes.  BTW, all rebuilds in the past minutes had configure run
automatically and succeeded without problems.  So maybe the issue is
resolved.

martin



  reply	other threads:[~2017-03-07 16:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-05 10:20 Build failure on Windows martin rudalics
2017-03-05 11:03 ` Andy Moreton
2017-03-05 13:27   ` martin rudalics
2017-03-05 15:23     ` Eli Zaretskii
2017-03-05 17:59       ` martin rudalics
2017-03-05 18:32         ` martin rudalics
2017-03-05 20:03           ` Eli Zaretskii
2017-03-05 21:28             ` martin rudalics
2017-03-06  3:27               ` Eli Zaretskii
2017-03-06  8:10                 ` martin rudalics
2017-03-05 20:02         ` Eli Zaretskii
2017-03-05 21:28           ` martin rudalics
2017-03-05 21:38             ` Paul Eggert
2017-03-06  3:30               ` Eli Zaretskii
2017-03-06  3:29             ` Eli Zaretskii
2017-03-06  8:11               ` martin rudalics
2017-03-06 16:08                 ` Eli Zaretskii
2017-03-06 17:45                   ` martin rudalics
2017-03-06 18:48                     ` Eli Zaretskii
2017-03-07  9:45                       ` martin rudalics
2017-03-07 15:44                         ` Eli Zaretskii
2017-03-07 16:13                           ` martin rudalics [this message]
2017-03-07 16:23                             ` Eli Zaretskii
2017-03-05 15:19   ` Eli Zaretskii
2017-03-05 18:10     ` Andy Moreton
2017-03-05 20:06       ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2004-03-11 18:28 Eric Hanchrow

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=58BEDC37.7020405@gmx.at \
    --to=rudalics@gmx.at \
    --cc=andrewjmoreton@gmail.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 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).