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 19:06:34 +0200 [thread overview]
Message-ID: <83a6tre09x.fsf@gnu.org> (raw)
In-Reply-To: <87czyn473v.fsf@optonline.net> (message from William C Doughty III on Sat, 02 Jan 2021 11:49:08 -0500)
> From: William C Doughty III <n2ocm@optonline.net>
> Cc: 45611@debbugs.gnu.org
> Date: Sat, 02 Jan 2021 11:49:08 -0500
>
> > 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?
>
> Your guess is as good ( or better ) than mine. I'm not too
> familiar with how these scripts work. And as far as config.log
> the check for XRenderQueryExyension in -lXrender it's not there
> at all.
>
> I just checked the version of autoconf. It's 2.69. So either
> This commit borked the config setup. Or somthing else is going
> on. As I said backing out this commit make the config and
> compile happy. BTW. this commit was the last I saw that
> affected configure.ac
I'm not sure this is the culprit. At least on my system, I still see
the test for Xrender after that commit.
next prev parent reply other threads:[~2021-01-02 17:06 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
2021-01-02 16:49 ` William C Doughty III
2021-01-02 17:06 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a6tre09x.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.