From: Paul Eggert <eggert@cs.ucla.edu>
To: Nils Ackermann <nils@ackermath.info>
Cc: emacs-devel@gnu.org
Subject: Re: build failure on emacs25 branch (c45a1ca) on Ubuntu 15.04
Date: Fri, 4 Mar 2016 19:49:22 -0800 [thread overview]
Message-ID: <56DA5742.5050704@cs.ucla.edu> (raw)
In-Reply-To: <87mvqdya0y.fsf@lejimdubmushnak.com>
Nils Ackermann wrote:
> Wrong type argument: number-or-marker-p, #[257 "ÀÁ.DÂ.DE‡" [and symbolp eieio--class-v]
This looks like the sort of thing 'make bootstrap' should fix; have you tried
that? If not, try building from a fresh checkout from git. The latter works for
me on Ubuntu 15.10 x86-64 with LC_ALL='en_US.utf8', emacs-25 commit
c45a1ca3c4eed56be6ad8086dcc805a86bc5935c.
next prev parent reply other threads:[~2016-03-05 3:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 1:43 build failure on emacs25 branch (c45a1ca) on Ubuntu 15.04 Nils Ackermann
2016-03-05 3:49 ` Paul Eggert [this message]
2016-03-05 17:33 ` Nils Ackermann
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=56DA5742.5050704@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=nils@ackermath.info \
/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).