From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: strange build problem with missing -by.el and -wy.el files
Date: Tue, 01 Nov 2022 09:04:00 +0200 [thread overview]
Message-ID: <83v8nzcg0v.fsf@gnu.org> (raw)
In-Reply-To: <87bkprbq6u.fsf@no.workgroup> (message from Gregor Zattler on Mon, 31 Oct 2022 23:09:45 +0100)
> From: Gregor Zattler <telegraph@gmx.net>
> Date: Mon, 31 Oct 2022 23:09:45 +0100
>
> In toplevel form:
> cedet/semantic/bovine/c.el:35:2: Error: Cannot open load file: No such file or directory, semantic/bovine/c-by
> make[4]: *** [Makefile:332: cedet/semantic/bovine/c.elc] Error 1
> make[4]: Leaving directory '/home/grfz/src/emacs-master-next/lisp'
> make[3]: *** [Makefile:366: compile-main] Error 2
> make[3]: Leaving directory '/home/grfz/src/emacs-master-next/lisp'
> make[2]: *** [Makefile:531: lisp] Error 2
> make[2]: Leaving directory '/home/grfz/src/emacs-master-next'
> make[2]: Entering directory '/home/grfz/src/emacs-master-next'
> ***
> *** "make all" failed with exit status 2.
> ***
> *** You could try to:
> *** - run "make bootstrap", which might fix the problem
> *** - run "make V=1", which displays the full commands invoked by make,
> *** to further investigate the problem
> ***
> make[2]: *** [Makefile:413: advice-on-failure] Error 2
> make[2]: Leaving directory '/home/grfz/src/emacs-master-next'
> make[1]: *** [Makefile:370: all] Error 2
> make[1]: Leaving directory '/home/grfz/src/emacs-master-next'
> make: *** [GNUmakefile:95: default] Error 2
>
> Line 35 in lisp/cedet/semantic/bovine/c.el reads:
>
> (require 'semantic/bovine/c-by)
>
> There is no semantic/bovine/c-by.el in the tree, but
> cedet/Changelog.1 says it was removed in 2013-11-30 together
> with other generated files.
It was removed from Git, but it gets regenerated as part of the
build.
> c-by.el starts this way:
So you do have c-by.el in the tree? Now I'm confused.
> so perhaps we should arrange for all the .elc files needed by semantic/lex and/or semantic/bovine to be present, before compiling c-by.el."
>
>
> but make -j 1 did not help.
>
> So I copied several .el files which were not generated from
> a not so old installation of emacs, like so:
That's the wrong way of handling the problem.
You need to understand why c-by.el is not generated as part of the
build. It's supposed to be generated by the rules in
admin/grammars/Makefile.in, which run early on during the build. It
is run via the rule in lisp/Makefile.in for the target "semantic",
look around line 415 in that file. Why doesn't that happen in your
case?
next prev parent reply other threads:[~2022-11-01 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 22:09 strange build problem with missing -by.el and -wy.el files Gregor Zattler
2022-11-01 7:04 ` Eli Zaretskii [this message]
2022-11-01 15:38 ` Gregor Zattler
2022-11-01 16:48 ` 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=83v8nzcg0v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).