From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56551@debbugs.gnu.org
Subject: bug#56551: 29.0.50; Errors in xterm.c when building --without-all
Date: Thu, 14 Jul 2022 07:50:33 -0700 [thread overview]
Message-ID: <CADwFkm=DusBeFU7aN-iVo82d_5Rs0Xkw7vCmhhW_cRsU7rYTYQ@mail.gmail.com> (raw)
In-Reply-To: <83edynu846.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> Did I succeed to fix this now?
Thanks, it builds now. These warnings remain, in case they're worth
fixing:
xterm.c: In function ‘x_scroll_bar_expose’:
xterm.c:14970:20: warning: variable ‘height’ set but not used
[-Wunused-but-set-variable]
14970 | int x, y, width, height;
| ^~~~~~
xterm.c:14970:13: warning: variable ‘width’ set but not used
[-Wunused-but-set-variable]
14970 | int x, y, width, height;
| ^~~~~
xterm.c:14970:10: warning: variable ‘y’ set but not used
[-Wunused-but-set-variable]
14970 | int x, y, width, height;
| ^
xterm.c:14970:7: warning: variable ‘x’ set but not used
[-Wunused-but-set-variable]
14970 | int x, y, width, height;
| ^
xterm.c: In function ‘mark_xterm’:
xterm.c:27942:7: warning: unused variable ‘i’ [-Wunused-variable]
27942 | int i;
| ^
In file included from gtkutil.c:29:
gtkutil.c: In function ‘xg_free_frame_widgets’:
gtkutil.c:1890:17: warning: implicit declaration of function
‘FRAME_X_DOUBLE_BUFFERED_P’ [-Wimplicit-function-declaration]
1890 | eassert (!FRAME_X_DOUBLE_BUFFERED_P (f));
| ^~~~~~~~~~~~~~~~~~~~~~~~~
lisp.h:174:43: note: in definition of macro ‘eassert’
174 | # define eassert(cond) ((void) (false && (cond))) /* Check
COND compiles. */
| ^~~~
gtkutil.c:1890:17: warning: nested extern declaration of
‘FRAME_X_DOUBLE_BUFFERED_P’ [-Wnested-externs]
1890 | eassert (!FRAME_X_DOUBLE_BUFFERED_P (f));
| ^~~~~~~~~~~~~~~~~~~~~~~~~
lisp.h:174:43: note: in definition of macro ‘eassert’
174 | # define eassert(cond) ((void) (false && (cond))) /* Check
COND compiles. */
| ^~~~
next prev parent reply other threads:[~2022-07-14 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 11:47 bug#56551: 29.0.50; Errors in xterm.c when building --without-all Stefan Kangas
2022-07-14 13:38 ` Eli Zaretskii
2022-07-14 14:50 ` Stefan Kangas [this message]
2022-07-14 15:13 ` Glenn Morris
2022-07-14 16:01 ` Eli Zaretskii
2022-07-15 2:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 15:18 ` 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='CADwFkm=DusBeFU7aN-iVo82d_5Rs0Xkw7vCmhhW_cRsU7rYTYQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=56551@debbugs.gnu.org \
--cc=eliz@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.
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).