From: Eli Zaretskii <eliz@gnu.org>
To: William C Doughty III <n2ocm@optonline.net>
Cc: 45611@debbugs.gnu.org
Subject: bug#45611: 28.0.50; xterm.c compile anomaly and link failure
Date: Sat, 02 Jan 2021 18:20:27 +0200 [thread overview]
Message-ID: <83im8fe2es.fsf@gnu.org> (raw)
In-Reply-To: <87h7nz4c0c.fsf@optonline.net> (message from William C Doughty III on Sat, 02 Jan 2021 10:03:15 -0500)
[Please use Reply All to keep the bug address on the CC list.]
> From: William C Doughty III <n2ocm@optonline.net>
> Date: Sat, 02 Jan 2021 10:03:15 -0500
>
> >> Needed to manually set HAVE_XRENDER and add -lXrender
> >> to src/Makefile, after this the make compiles xterm.c
> >> cleanly and the link for temacs succeeds.
> >
> > Please show the part of config.log where it tests for Xrender
> > availability.
> >
> > Thanks.
>
> >From the config.log , at least I think that's the section.
>
> | #define USE_XIM 1
> | #define XRegisterIMInstantiateCallback_arg6 XPointer
> | /* end confdefs.h. */
> | #include <X11/Intrinsic.h>
> | #include <X11/extensions/Xrender.h>
> |
> | int
> | main ()
> | {
> | return !XRenderQueryExtension;
> | ;
> | return 0;
> | }
Yes, but please show all the rest, starting with "checking for
XRenderQueryExtension in -lXrender" and ending with "$? = ..." after
the test. The test program is printed _after_ the stuff I want to
see, in particular the error messages that failed the compilation of
the test program.
> configure:14699: checking for cairo >= 1.8.0
> configure:14706: $PKG_CONFIG --exists --print-errors "$CAIRO_MODULE"
> configure:14709: $? = 0
> configure:14723: $PKG_CONFIG --exists --print-errors "$CAIRO_MODULE"
> configure:14726: $? = 0
> configure:14764: result
This the next test, so it is not relevant.
> The below if from the last time I tried a a compile from
> master. This is on a Fedora 32 system after :
Strange, it looks like the test for XRender was not done at all...
On my system that test is between these two:
> checking for inotify_init1... yes
> checking for cairo >= 1.8.0... yes
It says:
checking for XRenderQueryExtension in -lXrender... yes
Why isn't that test being run on your system?
next prev parent reply other threads:[~2021-01-02 16:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-02 12:20 bug#45611: 28.0.50; xterm.c compile anomaly and link failure William C Doughty III
2021-01-02 14:42 ` Eli Zaretskii
[not found] ` <87h7nz4c0c.fsf@optonline.net>
2021-01-02 16:20 ` Eli Zaretskii [this message]
2021-01-02 16:49 ` William C Doughty III
2021-01-02 17:06 ` Eli Zaretskii
2021-01-02 17:32 ` William C Doughty III
2021-01-02 17:48 ` Eli Zaretskii
[not found] ` <871rf343fq.fsf@optonline.net>
2021-01-02 18:27 ` Eli Zaretskii
2021-01-02 20:16 ` William C Doughty III
2021-01-02 20:23 ` Eli Zaretskii
2021-01-02 16:38 ` Michael Schmidt
2021-01-02 19:28 ` Michael Schmidt
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=83im8fe2es.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45611@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).