From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: ulm@gentoo.org, 68842@debbugs.gnu.org
Subject: bug#68842: 29.2; implicit declaration of function 'XOpenDisplay'
Date: Thu, 01 Feb 2024 11:03:06 +0200 [thread overview]
Message-ID: <86a5ok1rqt.fsf@gnu.org> (raw)
In-Reply-To: <87y1c4mv4k.fsf@yahoo.com> (message from Po Lu on Thu, 01 Feb 2024 16:44:27 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: ulm@gentoo.org, 68842@debbugs.gnu.org
> Date: Thu, 01 Feb 2024 16:44:27 +0800
>
> Po Lu <luangruo@yahoo.com> writes:
>
> > In that event, I see no problems with Ulrich's patch, as the configure
> > check is careful enough not to set emacs_cv_b_link=yes if that flag
> > doesn't work.
Thanks. Ulrich, please install the patch on the emacs-29 branch.
> Also FTR this flag isn't a requirement under GCC 4.6. It's only
> relevant for ancient versions of Binutils on Linux-based systems with
> a.out binaries, which are a rare sight if not nonexistent today,
> considering the exceedingly short half-lives of such systems.
OK. Still, my point was that we don't usually remove support for
anything on a release branch, only on master.
next prev parent reply other threads:[~2024-02-01 9:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 8:03 bug#68842: 29.2; implicit declaration of function 'XOpenDisplay' Ulrich Müller
2024-01-31 17:26 ` Eli Zaretskii
2024-01-31 19:16 ` Ulrich Mueller
2024-01-31 19:32 ` Eli Zaretskii
2024-02-01 1:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-01 7:38 ` Eli Zaretskii
2024-02-01 8:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-01 8:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-01 9:03 ` Eli Zaretskii [this message]
2024-02-01 9:21 ` Ulrich Mueller
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=86a5ok1rqt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68842@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=ulm@gentoo.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 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.