From: Jean Louis <bugs@gnu.support>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Glenn Morris <rgm@gnu.org>, 47159@debbugs.gnu.org
Subject: bug#47159: 28.0.50; gnutls not recognized in build process without pkg-config
Date: Sat, 20 Mar 2021 09:44:11 +0300 [thread overview]
Message-ID: <YFWZu4eTA2J3S+MV@protected.localdomain> (raw)
In-Reply-To: <87tup7o9p6.fsf@gnus.org>
* Lars Ingebrigtsen <larsi@gnus.org> [2021-03-19 11:00]:
> Glenn Morris <rgm@gnu.org> writes:
>
> >> I can't see any explicit checks for pkg-config in configure.ac.
> >
> > PKG_PROG_PKG_CONFIG(0.9.0)
> >
> > Perhaps you want to check the result of that and make it fatal,
> > but only in some cases. Or perhaps users should read configure output.
>
> Ah, thanks. I've now added a warning about this just above the error
> about the missing library, so that should help, and probably not lead to
> too many false positives.
I have now done git pull and removed pkg-config from system
temporarily, this below is the message I got, even though I do have
gnutls in the system.
...
checking for pkg-config... no
...
checking for GifMakeMapObject in -lgif... yes
configure: error: The following required libraries were not found:
gnutls
Maybe some development libraries/packages are missing?
To build anyway, give:
--with-gnutls=ifavailable
as options to configure.
next prev parent reply other threads:[~2021-03-20 6:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 12:53 bug#47159: 28.0.50; gnutls not recognized in build process without pkg-config Jean Louis
2021-03-18 5:52 ` Lars Ingebrigtsen
2021-03-18 10:59 ` Jean Louis
2021-03-18 11:24 ` Eli Zaretskii
2021-03-19 9:09 ` Jean Louis
2021-03-19 11:46 ` Eli Zaretskii
2021-03-18 11:22 ` Eli Zaretskii
2021-03-18 15:26 ` Glenn Morris
2021-03-19 7:59 ` Lars Ingebrigtsen
2021-03-20 6:44 ` Jean Louis [this message]
2021-03-20 7:52 ` Lars Ingebrigtsen
2021-03-21 13:39 ` Jean Louis
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=YFWZu4eTA2J3S+MV@protected.localdomain \
--to=bugs@gnu.support \
--cc=47159@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rgm@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 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.