unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, "Jan D." <jan.h.d@swipnet.se>,
	emacs-devel@gnu.org
Subject: Re: pkg-config required on OSX, why?
Date: Fri, 16 May 2014 11:52:30 -0400	[thread overview]
Message-ID: <jwvbnuxoham.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <53761FBA.1090709@cs.ucla.edu> (Paul Eggert's message of "Fri, 16 May 2014 07:24:58 -0700")

> 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.

Please do that.  Building from Bazaar (or Git) is an important use case.


        Stefan "who sees the case of building from a tarball as the exception
                rather than the rule"



  reply	other threads:[~2014-05-16 15:52 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
2014-05-16 15:52       ` Stefan Monnier [this message]
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=jwvbnuxoham.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=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).