From: Tim Cross <theophilusx@gmail.com>
To: emacs-devel@gnu.org
Subject: Git master head build failure?
Date: Thu, 01 Apr 2021 13:41:49 +1100 [thread overview]
Message-ID: <875z16en2o.fsf@gmail.com> (raw)
Trying to build from current git head (rev:168d2628b23333) and getting
the following error
In toplevel form:
cedet/semantic/bovine/c.el:35:1: Error: Loading file /home/tim/git/emacs/lisp/cedet/semantic/bovine/c-by.elc failed to provide feature ‘semantic/bovine/c-by’
make[2]: *** [Makefile:279: cedet/semantic/bovine/c.elc] Error 1
make[2]: Leaving directory '/home/tim/git/emacs/lisp'
make[1]: *** [Makefile:302: compile-main] Error 2
make[1]: Leaving directory '/home/tim/git/emacs/lisp'
make: *** [Makefile:398: lisp] Error 2
Tried the following -
git pull
make maintainer-clean
./autogen.sh
./configure
make
also tried make bootstrap.
This is in a repo which previously had the emacs-27 branch checked out.
Now has the master branch checked out.
Is this a known issue or have I missed something?
Platform is Linux (Ubuntu 20.10).
--
Tim Cross
next reply other threads:[~2021-04-01 2:41 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 2:41 Tim Cross [this message]
2021-04-01 3:04 ` Git master head build failure? Stefan Monnier
2021-04-01 3:10 ` Tim Cross
2021-04-01 7:33 ` Eli Zaretskii
2021-04-01 8:57 ` Tim Cross
2021-04-01 9:17 ` tomas
2021-04-01 9:56 ` Daniel Brooks
2021-04-01 9:36 ` Gregor Zattler
2021-04-01 10:11 ` Andreas Schwab
2021-04-01 7:25 ` Eli Zaretskii
2021-04-01 8:34 ` Tim Cross
2021-04-01 9:00 ` Eli Zaretskii
2021-04-01 10:56 ` Stefan Kangas
2021-04-01 13:03 ` Eli Zaretskii
2021-04-01 13:32 ` Stefan Kangas
2021-04-01 13:02 ` Eli Zaretskii
2021-04-01 13:01 ` Eli Zaretskii
2021-04-01 13:03 ` Stefan Monnier
2021-04-01 13:07 ` Eli Zaretskii
2021-04-01 13:32 ` Stefan Kangas
2021-04-01 13:36 ` Eli Zaretskii
2021-04-01 15:32 ` Stefan Monnier
2021-04-01 15:37 ` Eli Zaretskii
2021-04-01 16:05 ` extraclean and admin/grammars [was Re: Git master head build failure?] Glenn Morris
2021-04-01 16:09 ` Lars Ingebrigtsen
2021-04-01 16:19 ` Lars Ingebrigtsen
2021-04-02 4:19 ` Tim Cross
2021-04-02 5:58 ` Eli Zaretskii
2021-04-02 13:41 ` Lars Ingebrigtsen
2021-04-02 13:58 ` Eli Zaretskii
2021-04-01 18:31 ` Eli Zaretskii
2021-04-02 13:40 ` Lars Ingebrigtsen
2021-04-02 13:57 ` Eli Zaretskii
2021-04-03 13:30 ` Lars Ingebrigtsen
2021-04-03 14:15 ` Eli Zaretskii
2021-04-03 22:36 ` chad
2021-04-04 7:20 ` Eli Zaretskii
2021-04-03 23:52 ` Tim Cross
2021-04-04 7:39 ` Eli Zaretskii
2021-04-04 19:44 ` Lars Ingebrigtsen
2021-04-01 17:15 ` Stefan Monnier
2021-04-01 19:56 ` Eli Zaretskii
2021-04-01 20:13 ` Stefan Monnier
2021-04-03 7:58 ` Eli Zaretskii
2021-04-13 2:20 ` Stefan Monnier
2021-04-13 11:51 ` Eli Zaretskii
2021-04-13 12:19 ` Eli Zaretskii
2021-04-13 13:01 ` Stefan Monnier
2021-04-13 12:59 ` Stefan Monnier
2021-04-13 14:03 ` Eli Zaretskii
2021-04-01 18:29 ` Eli Zaretskii
2021-04-04 16:28 ` Glenn Morris
2021-04-04 17:12 ` Eli Zaretskii
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=875z16en2o.fsf@gmail.com \
--to=theophilusx@gmail.com \
--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).