From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 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 12:58:07 +0100 [thread overview]
Message-ID: <87a6uj5j8w.fsf@gnus.org> (raw)
In-Reply-To: <X9StGnkVqlCJtIPR@ACM> (Alan Mackenzie's message of "Sat, 12 Dec 2020 11:44:26 +0000")
Alan Mackenzie <acm@muc.de> writes:
> 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 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!
:-)
I'd suggest pulling down a clean Emacs tree to see whether the problem
is present there, too... or perhaps use a "make extraclean" (I think
that's the target that'll remove everything, even more than "bootstrap")
and see whether that helps.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-12 11:58 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
2020-12-12 11:58 ` Lars Ingebrigtsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6uj5j8w.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=45186@debbugs.gnu.org \
--cc=acm@muc.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.