From: Eli Zaretskii <eliz@gnu.org>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: 50520-done@debbugs.gnu.org
Subject: bug#50520: GNU emacs commit 2e595b3e8b8870 fails to build on Debian GNU/Linux bookworm/sid (x86-64)
Date: Sat, 11 Sep 2021 19:05:04 +0300 [thread overview]
Message-ID: <83czpfgksv.fsf@gnu.org> (raw)
In-Reply-To: <c98dcde3-451b-781c-fa74-741c88958990@starynkevitch.net> (message from Basile Starynkevitch on Sat, 11 Sep 2021 13:35:08 +0200)
> From: Basile Starynkevitch <basile@starynkevitch.net>
> Date: Sat, 11 Sep 2021 13:35:08 +0200
>
> I am often compiling the latest GNU emacs snapshot, and generally with success.
>
> Today it fails with:
>
> guiseppe.x86_64 src/Editors/emacs 13:33 .0 % make
> make -C lib all
> make[1]: Entering directory '/usr/src/Editors/emacs/lib'
> make[1]: Nothing to be done for 'all'.
> make[1]: Leaving directory '/usr/src/Editors/emacs/lib'
> make -C lib-src all
> make[1]: Entering directory '/usr/src/Editors/emacs/lib-src'
> make[1]: Nothing to be done for 'all'.
> make[1]: Leaving directory '/usr/src/Editors/emacs/lib-src'
> make -C src VCSWITNESS='$(srcdir)/../.git/logs/HEAD' BIN_DESTDIR=''/usr/local/bin/'' \
> ELN_DESTDIR='/usr/local/lib/emacs/28.0.50/' all
> make[1]: Entering directory '/usr/src/Editors/emacs/src'
> CC keyboard.o
> keyboard.c: In function ‘make_lispy_position’:
> keyboard.c:5108:23: error: ‘struct frame’ has no member named ‘tool_bar_window’; did you mean ‘tab_bar_window’?
> 5108 | || (WINDOWP (f->tool_bar_window)
> | ^~~~~~~~~~~~~~~
> | tab_bar_window
This has been solved recently, please update from Git and try again.
prev parent reply other threads:[~2021-09-11 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 11:35 bug#50520: GNU emacs commit 2e595b3e8b8870 fails to build on Debian GNU/Linux bookworm/sid (x86-64) Basile Starynkevitch
2021-09-11 16:05 ` Eli Zaretskii [this message]
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=83czpfgksv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50520-done@debbugs.gnu.org \
--cc=basile@starynkevitch.net \
/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).