From: Eli Zaretskii <eliz@gnu.org>
To: William C Doughty III <n2ocm@optonline.net>
Cc: 45611-done@debbugs.gnu.org
Subject: bug#45611: 28.0.50; xterm.c compile anomaly and link failure
Date: Sat, 02 Jan 2021 22:23:13 +0200 [thread overview]
Message-ID: <83v9cfcclq.fsf@gnu.org> (raw)
In-Reply-To: <87v9cf2ixo.fsf@optonline.net> (message from William C Doughty III on Sat, 02 Jan 2021 15:16:35 -0500)
> From: William C Doughty III <n2ocm@optonline.net>
> Cc: 45611@debbugs.gnu.org
> Date: Sat, 02 Jan 2021 15:16:35 -0500
>
> > 119 | #include <X11/Intrinsic.h>
> > | ^~~~~~~~~~~~~~~~~
> > compilation terminated.
> >
> > Your X11 headers seem to be in bad shape. Maybe you need to
> > re-install some development package(s)?
> >
>
> Yup that was definitely it. Installed dev packages for libXt. The compile
> now works. I think a new dependency has just been added. The patch I had
> a problem with looks like it added it. Things have compiled cleanly in
> the past without those libraries (at least with how I was configuring
> the emacs compile in the past). Oh well, it's fixed here now.
Thanks, I'm therefore closing this bug.
next prev parent reply other threads:[~2021-01-02 20:23 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
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 [this message]
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=83v9cfcclq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45611-done@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).