From: Alan Mackenzie <acm@muc.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: acm@muc.de, 45186@debbugs.gnu.org
Subject: bug#45186: Emacs master: build broken by spurious message ".../c-by.elc failed to provide feature `semantic/bovine/c-by"
Date: Sat, 12 Dec 2020 11:44:26 +0000 [thread overview]
Message-ID: <X9StGnkVqlCJtIPR@ACM> (raw)
In-Reply-To: <878sa4840k.fsf@gnus.org>
Hello, Lars.
On Fri, Dec 11, 2020 at 21:46:35 +0100, Lars Ingebrigtsen wrote:
> Alan Mackenzie <acm@muc.de> writes:
> > I've just updated a master repo here, and tried a make bootstrap.
> > I get the error message:
> > cedet/semantic/bovine/c.el:35:1: Error: Loading file
> > /home/acm/emacs/emacs.git/sub-master-a/lisp/cedet/semantic/bovine/c-by.elc
> > failed to provide feature `semantic/bovine/c-by'
> I tried a "make bootstrap" on the current trunk now (on
> Debian/bullseye), and I did not get that error message...
Thanks for looking at it.
I got the error message again this morning (it wasn't just a bad dream),
and I'm trying to think how it could have happened.
The way of calling require
(require 'semantic/bovine/c-by)
with the path included in the required symbol is totally new to me. It
just seems like a wrong thing to do. But it's been working for many
years, obviously, for some value of "working".
I do a git status, and notice amongs my untracked files list:
lisp/cedet/semantic/wisent/java-tags-wy.el
lisp/cedet/srecode/srecode-template-wy.el
, so I've deleted these. It hasn't helped.
I've inserted a
(provide 'semantic/bovine/c-by)
into c-by.el. Now I get other errors:
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
In toplevel form:
cedet/semantic/wisent/js-wy.el:58:17: Error: Bad input grammar
make[2]: *** [Makefile:295: cedet/semantic/wisent/js-wy.elc] Error 1
make[2]: *** Waiting for unfinished jobs....
In toplevel form:
cedet/semantic/wisent/javascript.el:31:1: Error: Bad input grammar
make[2]: *** [Makefile:295: cedet/semantic/wisent/javascript.elc] Error
1
In toplevel form:
cedet/semantic/wisent/python-wy.el:58:17: Error: Symbol `SEMICOLON' is
used, but is not defined as a token and has no rules
make[2]: *** [Makefile:295: cedet/semantic/wisent/python-wy.elc] Error 1
In toplevel form:
cedet/semantic/wisent/python.el:37:1: Error: Symbol `SEMICOLON' is used,
but is not defined as a token and has no rules
make[2]: *** [Makefile:295: cedet/semantic/wisent/python.elc] Error 1
In end of data:
cedet/semantic/bovine/c.el:2272:1: Warning: the function
`semantic-c-by--install-parser' is not known to be defined.
make[2]: Leaving directory '/home/acm/emacs/emacs.git/sub-master-a/lisp'
make[1]: *** [Makefile:318: compile-main] Error 2
make[1]: Leaving directory '/home/acm/emacs/emacs.git/sub-master-a/lisp'
make: *** [Makefile:411: lisp] Error 2
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
. The word SEMICOLON doesn't appear anywhere in the git log. I really
don't want to start burrowing through the internals of the cedet things.
I don't understand how Emacs is building for everybody else but not me.
I've tried reconfiguring my Emacs with no options to ./configure. This
hasn't helped either.
Perhaps this conversation would be better on emacs-devel. Anyhow thanks
for your patience in reading this miserable post!
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2020-12-12 11:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 20:31 bug#45186: Emacs master: build broken by spurious message ".../c-by.elc failed to provide feature `semantic/bovine/c-by" Alan Mackenzie
2020-12-11 20:46 ` Lars Ingebrigtsen
2020-12-12 11:44 ` Alan Mackenzie [this message]
2020-12-12 11:58 ` Lars Ingebrigtsen
2020-12-12 12:50 ` Alan Mackenzie
2020-12-12 12:53 ` Alan Mackenzie
2020-12-12 13:17 ` Lars Ingebrigtsen
2020-12-12 14:31 ` 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=X9StGnkVqlCJtIPR@ACM \
--to=acm@muc.de \
--cc=45186@debbugs.gnu.org \
--cc=larsi@gnus.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).