unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: jtbx@disroot.org, yuri.v.khan@gmail.com, emacs-devel@gnu.org
Subject: Re: configure fails to find gtk and glib and exits with an empty error
Date: Thu, 08 Feb 2024 07:50:04 +0200	[thread overview]
Message-ID: <86jznfy06r.fsf@gnu.org> (raw)
In-Reply-To: <87h6ikm39m.fsf@> (message from Björn Bidar on Wed, 07 Feb 2024 22:24:21 +0200)

> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Cc: "Jeremy Baxter" <jtbx@disroot.org>,  yuri.v.khan@gmail.com,
>   emacs-devel@gnu.org
> Date: Wed, 07 Feb 2024 22:24:21 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > OK, thanks.  So I guess we can consider this issue resolved.
> >
> > (In general, I think pkg-config should be installed on any system
> > where users build software by running Autoconf tools.)
> 
> In most cases pkg-config is provided by pkgconf as pkg-config isn't
> maintained anymore (last release was 2017).

I meant pkg-config the program.  If pkgconf provides it, then having
that installed will do; otherwise, Someone™ should tell Autoconf
developers to start supporting pkgconf in their scripts and m4 macros.



      parent reply	other threads:[~2024-02-08  5:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-13  4:52 configure fails to find gtk and glib and exits with an empty error Jeremy Baxter
2024-01-13 10:13 ` Eli Zaretskii
2024-01-13 18:16   ` Jeremy Baxter
2024-01-13 18:47     ` Eli Zaretskii
2024-01-13 18:55       ` Jeremy Baxter
2024-01-13 20:15 ` Yuri Khan
2024-01-13 20:21   ` Jeremy Baxter
2024-01-14  6:12     ` Eli Zaretskii
2024-01-14 18:44       ` Jeremy Baxter
2024-01-14 19:05         ` Eli Zaretskii
2024-02-07 20:24           ` Björn Bidar
     [not found]           ` <87h6ikm39m.fsf@>
2024-02-08  5:50             ` Eli Zaretskii [this message]

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=86jznfy06r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bjorn.bidar@thaodan.de \
    --cc=emacs-devel@gnu.org \
    --cc=jtbx@disroot.org \
    --cc=yuri.v.khan@gmail.com \
    /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).