From: Paul Eggert <eggert@cs.ucla.edu>
To: "Jan D." <jan.h.d@swipnet.se>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: pkg-config required on OSX, why?
Date: Fri, 16 May 2014 07:24:58 -0700 [thread overview]
Message-ID: <53761FBA.1090709@cs.ucla.edu> (raw)
In-Reply-To: <537614E8.7050401@swipnet.se>
Jan D. wrote:
> having pkg-config as a requirement form some macros must mean those
> macros are important. What are they?
Among other things, the macros test whether pkg-config is present, and
they do the right thing when pkg-config is absent. One needs the macros
only to run 'autoconf' etc., not to run 'configure'.
It does strike me, though, that this new requirement to have pkg-config
installed (and in the same place that automake is installed) is a pain.
I ran afoul of it myself not five minutes ago, since I use my own
automake. I'm inclined to have us copy pkg.m4 into m4, using a new tool
(admin/merge-pkg-config, say). That way, someone can periodically
upgrade to the latest pkg.m4 manually, and the rest of us won't have to
worry about having pkg-config installed correctly.
next prev parent reply other threads:[~2014-05-16 14:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 11:01 pkg-config required on OSX, why? Jan D.
2014-05-16 13:07 ` Eli Zaretskii
2014-05-16 13:38 ` Jan D.
2014-05-16 14:24 ` Paul Eggert [this message]
2014-05-16 15:52 ` Stefan Monnier
2014-05-16 15:52 ` Paul Eggert
2014-05-16 16:48 ` Glenn Morris
2014-05-16 16:50 ` Jan D.
2014-05-16 19:04 ` Paul Eggert
2014-05-17 6:41 ` Jan Djärv
2014-05-16 15:57 ` Glenn Morris
2014-05-16 16:39 ` Jan D.
2014-05-16 16:46 ` Glenn Morris
2014-05-16 17:45 ` Jan D.
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=53761FBA.1090709@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
/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).