unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 47159@debbugs.gnu.org
Subject: bug#47159: 28.0.50; gnutls not recognized in build process without pkg-config
Date: Thu, 18 Mar 2021 13:59:13 +0300	[thread overview]
Message-ID: <YFMygUjz+FnkrF/i@protected.localdomain> (raw)
In-Reply-To: <87sg4trotr.fsf@gnus.org>

* Lars Ingebrigtsen <larsi@gnus.org> [2021-03-18 08:52]:
> So I guess we should just add a check for pkg-config in the gnutls
> check?  Any opinions?

My opinion as a non-expert in the subject of preparation of
`configure' script is that it should check for any fundamental command
required for building.

Developers may forget those very basic packages/software as they
rarely develop from a plain system. The discovery came about because I
have been installing Parabola GNU/Linux-libre and did not know what is
the main virtual package to install all the other building tools
packages, so I was installing one by one whatever was missing, like
`automake' or `gcc' or similar packages until the point that I could
compile it.





  reply	other threads:[~2021-03-18 10:59 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 [this message]
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
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

  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=YFMygUjz+FnkrF/i@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=47159@debbugs.gnu.org \
    --cc=larsi@gnus.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).