From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: emacs-devel@gnu.org
Subject: Oddities in ./configure --with-pgtk's output
Date: Sun, 19 Dec 2021 11:15:33 +0100 [thread overview]
Message-ID: <878rwguchm.fsf@gmail.com> (raw)
Hello folks,
I diff'ed the output of "./configure" and "./configure --with-pgtk" out
of curiosity; there are a couple of things that I found intriguing.
Some of them might warrant a bug report; since I could very well be
missing something, I thought I'd report here first.
(This is on openSUSE Tumbleweed, on commit 2021-12-19 "Add missing
implementation of `pgtk-menu-bar-open'" (579d7c20da))
> -checking for libwebp >= 0.6.0... yes
IIUC 'configure' guards WebP support behind several 'test "${HAVE_XXX}"'
clauses where XXX represents "something that supports displaying
images". Should this be extended to ${HAVE_PGTK}?
> +checking for pkg-config... (cached) /usr/bin/pkg-config
> +checking pkg-config is at least version 0.16... yes
Not sure why this check is only present --with-pgtk?
> @@ -619,9 +592,9 @@
> Does Emacs use -lxml2? yes
> Does Emacs use -lfreetype? yes
> Does Emacs use HarfBuzz? yes
> - Does Emacs use -lm17n-flt? yes
> + Does Emacs use -lm17n-flt?
> Does Emacs use -lotf? yes
> - Does Emacs use -lxft? no
> + Does Emacs use -lxft?
> Does Emacs use -lsystemd? yes
> Does Emacs use -ljansson? yes
> Does Emacs use the GMP library? yes
Should -lm17n-flt and -lxft say "no" instead of being empty?
At any rate, thanks for all the hard work.
next reply other threads:[~2021-12-19 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 10:15 Kévin Le Gouguec [this message]
2021-12-19 10:28 ` Oddities in ./configure --with-pgtk's output Po Lu
2021-12-19 12:49 ` Kévin Le Gouguec
2021-12-19 12:53 ` Po Lu
2021-12-19 13:00 ` Lars Ingebrigtsen
2021-12-19 13:02 ` Po Lu
2021-12-19 13:59 ` Lars Ingebrigtsen
2021-12-20 1:24 ` Po Lu
2021-12-19 13:13 ` Eli Zaretskii
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=878rwguchm.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=emacs-devel@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).