From: Sean Whitton <spwhitton@spwhitton.name>
To: 56292@debbugs.gnu.org
Subject: bug#56292: 29.0.50; Compilation failure since recent loaddefs speed up
Date: Tue, 28 Jun 2022 22:20:14 -0700 [thread overview]
Message-ID: <87v8skavw1.fsf@melete.silentflame.com> (raw)
Hello,
When I try to byte compile bongo.el[1] with recent master I get this
strange error:
~/tmp/bongo.el:5341:35: Error: Wrong type argument: sequencep, 0
Line 5341 is this:
(defun bongo-player-update-elapsed-time (player elapsed-time)
"Set PLAYER's `elapsed-time' property to ELAPSED-TIME,
unless PLAYER's last seek happened less than N seconds ago, where N
is the value of PLAYER's `time-update-delay-after-seek' property."
(let ((delay (bongo-player-get player 'time-update-delay-after-seek)))
(when (or (null delay) (zerop delay)
(let ((time (bongo-player-get player 'last-seek-time)))
(or (null time)
(time-less-p (seconds-to-time delay)
>>>> this one >>>> (subtract-time (current-time) time)))))
(bongo-player-put player 'elapsed-time elapsed-time))))
which doesn't look suspicious.
Git bisection says 1d4e903417 is the first bad commit. I did a
bootstrap build for each step of the bisection, with this script:
git clean -xdff
make -j4 || exit 125
src/emacs --batch -f batch-byte-compile ~/tmp/bongo.el || exit 1
Presumably the error is coming from a type error somewhere in the
bytecompilation machinery, rather than this line in bongo.el?
[1] https://github.com/dbrock/bongo/blob/master/bongo.el
--
Sean Whitton
next reply other threads:[~2022-06-29 5:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 5:20 Sean Whitton [this message]
2022-06-29 10:23 ` bug#56292: 29.0.50; Compilation failure since recent loaddefs speed up Lars Ingebrigtsen
2022-06-29 15:43 ` Sean Whitton
2022-06-30 9:15 ` Lars Ingebrigtsen
2022-06-30 18:16 ` Sean Whitton
2022-06-30 18:21 ` Lars Ingebrigtsen
2022-08-02 11:08 ` bug#56292: 29.0.50; Problem with define-obsolete-function-alias in loaddefs.el Lars Ingebrigtsen
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=87v8skavw1.fsf@melete.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=56292@debbugs.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).