all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: joakim@verona.se
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: revno 101399 fails to build
Date: Fri, 10 Sep 2010 10:52:20 +0200	[thread overview]
Message-ID: <m37hiu56bf.fsf@verona.se> (raw)
In-Reply-To: <m31v92ro2w.fsf@hase.home> (Andreas Schwab's message of "Fri, 10 Sep 2010 10:37:43 +0200")

Andreas Schwab <schwab@linux-m68k.org> writes:

> joakim@verona.se writes:
>
>> ...
>> In toplevel form:
>> calc/calc-help.el:30:1:Error: Required feature `calc-ext' was not provided
>
> Do you build with more that one job in parallel?  In this case it can
> happen that one emacs process writes out the elc file while another one
> is reading the same (partial) file at the same time.  To fix that the
> creation of the elc file need to be made atomic.

Ok, given the current infrastructure, what combination of build commands
would be as reliable as possible and reasonably fast?

is it possible to do, in pseudo-code:

make -j4 all-c-targets && \
make elc-files && \
make -j4 all-other-stuff-requiring-c-targets-and-elc-files

This is for a build server, and I want very reliable build results.

I have/want nightly, slow,  code quality builds, and continus, fast, builds
polling bzr.


> Andreas.

-- 
Joakim Verona



  reply	other threads:[~2010-09-10  8:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10  5:40 revno 101399 fails to build joakim
2010-09-10  6:27 ` Glenn Morris
2010-09-10  7:48   ` joakim
2010-09-11  4:58     ` Stephen J. Turnbull
2010-09-13 12:08       ` Eli Zaretskii
2010-09-14 12:22         ` Stephen J. Turnbull
2010-09-10  8:37 ` Andreas Schwab
2010-09-10  8:52   ` joakim [this message]
2010-09-13 11:52   ` Eli Zaretskii
2010-09-13 15:52     ` Stefan Monnier
2010-09-13 17:05       ` Eli Zaretskii
2010-09-13 16:17     ` Glenn Morris

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=m37hiu56bf.fsf@verona.se \
    --to=joakim@verona.se \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.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.