From: "Jan D." <jan.h.d@swipnet.se>
To: "joakim@verona.se" <joakim@verona.se>
Cc: Alan Mackenzie <acm@muc.de>, "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: build broken: no defun org-float-time. Who's guilty, and what does he propose?
Date: Mon, 7 Sep 2009 12:30:00 +0200 [thread overview]
Message-ID: <D24A4FEC-416F-4EF8-9485-532F9DFA5E9E@swipnet.se> (raw)
In-Reply-To: <m31vmjqdxm.fsf@verona.se>
I think most problems comes from doing
cvs update
and then you get old .elc files left behind or you need to do
make bootstrap
again.
A make that removed old .elc files and did bootstrap when needed is
the ideal solution. The second part is probably very hard.
Jan D.
7 sep 2009 kl. 11.52 skrev joakim@verona.se:
> Alan Mackenzie <acm@muc.de> writes:
>
>> Hi, Emacs,
>>
>> I've just cvs updated, and the build breaks with:
>>
>> org/org-ascii.el:29:1:Error: Symbol's function definition is void:
>> org-float-time
>>
>> Could the person who's responsible please fix this.
>>
>> Here we go again. The endless tread mill of the broken build. It
>> feels
>> like being spat at. Sorry to be so "unhelpful", but I've got no
>> desire
>> or energy to keep debugging broken builds, or to keep "try make
>> bootstrap"ing. I'm going through a very bad patch in my personal
>> life,
>> and I just don't have the energy any more, and I'm not prepared to
>> do it.
>>
>> "cvs update" followed by "make" MUST WORK NEARLY ALL THE TIME.
>> Alternatively "bzr update", "make" working nearly all the time
>> would be
>> OK.
>>
>> This is a serious process bug we have, we've had for years, and we
>> MUST
>> fix. If it's not fixed soon, I'm just going to give up on Emacs
>> maintenance and bid the project goodbye. The pain level is too high.
>
> I've been interested in setting up an automatic build test environment
> for Emacs for some time. It would basically checkout the emacs sources
> on every checkin, build the sources and report the build
> quality(probably with some existing continuous integration software).
>
> I would also store a TB or something of past builds.
>
> Would that be of any help to you?
>
>
>> Sorry, and all that.
> --
> Joakim Verona
>
next prev parent reply other threads:[~2009-09-07 10:30 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 9:28 build broken: no defun org-float-time. Who's guilty, and what does he propose? Alan Mackenzie
2009-09-07 9:47 ` Andreas Schwab
2009-09-07 9:52 ` joakim
2009-09-07 10:09 ` Lennart Borgman
2009-09-07 11:37 ` joakim
2009-09-07 10:30 ` Jan D. [this message]
2009-09-07 17:42 ` Eli Zaretskii
2009-09-07 17:59 ` Ken Raeburn
2009-09-07 18:32 ` Drew Adams
2009-09-07 18:42 ` Lennart Borgman
2009-09-07 19:22 ` Ken Raeburn
2009-09-07 19:03 ` Glenn Morris
2009-09-07 19:20 ` Drew Adams
2009-09-07 20:08 ` Eli Zaretskii
2009-09-07 21:43 ` more reliable `make' Glenn Morris
2009-09-08 16:46 ` Stefan Monnier
2009-09-10 6:28 ` Glenn Morris
2009-09-10 13:37 ` Stefan Monnier
2009-09-07 20:59 ` build broken: no defun org-float-time. Who's guilty, and what does he propose? joakim
2009-09-07 21:39 ` Glenn Morris
2009-09-07 21:55 ` joakim
2009-09-07 21:13 ` Alan Mackenzie
2009-09-08 16:48 ` Stefan Monnier
2009-09-08 18:17 ` build broken: no defun org-float-time. A workaround Alan Mackenzie
2009-09-08 19:08 ` Ken Raeburn
2009-09-07 20:06 ` build broken: no defun org-float-time. Who's guilty, and what does he propose? Eli Zaretskii
2009-09-07 23:39 ` Ken Raeburn
2009-09-08 2:41 ` Stephen J. Turnbull
2009-09-08 3:20 ` Eli Zaretskii
2009-09-08 7:54 ` Ken Raeburn
2009-09-08 17:47 ` Eli Zaretskii
2009-09-08 18:32 ` Ken Raeburn
2009-09-08 17:01 ` Stefan Monnier
2009-09-08 17:51 ` Eli Zaretskii
2009-09-09 3:14 ` Stefan Monnier
2009-09-08 2:37 ` Stephen J. Turnbull
2009-09-08 3:14 ` Eli Zaretskii
2009-09-08 17:11 ` Stefan Monnier
2009-09-07 10:05 ` Miles Bader
2009-09-07 11:15 ` joakim
2009-09-07 13:35 ` Alan Mackenzie
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=D24A4FEC-416F-4EF8-9485-532F9DFA5E9E@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
/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).