From: Eli Zaretskii <eliz@gnu.org>
To: William C Doughty III <n2ocm@optonline.net>
Cc: 60884@debbugs.gnu.org
Subject: bug#60884: 30.0.50; Compile failure - followup
Date: Tue, 17 Jan 2023 19:46:02 +0200 [thread overview]
Message-ID: <83h6wp2gx1.fsf@gnu.org> (raw)
In-Reply-To: <87k01l17lr.fsf@optonline.net> (message from William C Doughty III on Tue, 17 Jan 2023 10:52:32 -0500)
merge 60884 60883
thanks
> From: William C Doughty III <n2ocm@optonline.net>
> Date: Tue, 17 Jan 2023 10:52:32 -0500
>
> With chrrent origin/master - compile results showing error:
>
> Compilation started at Tue Jan 17 10:47:14
>
> make -k
> make actual-all || make advice-on-failure make-target=all exit-status=$?
> make[1]: Entering directory '/home/n2ocm/Devel/emacs-dev/emacs'
> make -C lib all
> make[2]: Entering directory '/home/n2ocm/Devel/emacs-dev/emacs/lib'
> make[2]: Nothing to be done for 'all'.
> make[2]: Leaving directory '/home/n2ocm/Devel/emacs-dev/emacs/lib'
> make -C lib-src all
> make[2]: Entering directory '/home/n2ocm/Devel/emacs-dev/emacs/lib-src'
> make[2]: Nothing to be done for 'all'.
> make[2]: Leaving directory '/home/n2ocm/Devel/emacs-dev/emacs/lib-src'
> make -C src BIN_DESTDIR=''/usr/local/bin/'' \
> ELN_DESTDIR='/usr/local/lib/emacs/30.0.50/' all
> make[2]: Entering directory '/home/n2ocm/Devel/emacs-dev/emacs/src'
> GEN globals.h
> CC dispnew.o
> CC frame.o
> CC xdisp.o
> CC menu.o
> CC xmenu.o
> CC window.o
> CC ccl.o
> CC term.o
> CC terminal.o
> CC xfaces.o
> CC xterm.o
> xterm.c: In function 'handle_one_xevent':
> xterm.c:24495:26: error: 'struct frame' has no member named 'last_tool_bar_item'; did you mean 'last_tab_bar_item'?
> 24495 | if (f->last_tool_bar_item != -1)
> | ^~~~~~~~~~~~~~~~~~
> | last_tab_bar_item
> make[2]: *** [Makefile:425: xterm.o] Error 1
> CC xfns.o
> CC xselect.o
> CC xrdb.o
> CC xsmfns.o
> CC xsettings.o
> CC gtkutil.o
>
Thanks, but please don't report the same problem with different
Subject lines, because then the bug tracker creates a new issue for
each of your reports.
This should be fixed now on the master branch.
next prev parent reply other threads:[~2023-01-17 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 15:52 bug#60884: 30.0.50; Compile failure - followup William C Doughty III
2023-01-17 17:46 ` Eli Zaretskii [this message]
2023-09-06 0:07 ` Stefan Kangas
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=83h6wp2gx1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60884@debbugs.gnu.org \
--cc=n2ocm@optonline.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).