unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: pkg-config required on OSX, why?
Date: Fri, 16 May 2014 18:50:51 +0200	[thread overview]
Message-ID: <537641EB.5000905@swipnet.se> (raw)
In-Reply-To: <53763447.8050605@cs.ucla.edu>

Hello.

Paul Eggert skrev 2014-05-16 17:52:
> Paul Eggert wrote:
>> I'm inclined to have us copy pkg.m4 into m4
>
> I installed something along those lines, as trunk bzr 117116, so you
> shouldn't need pkg-config on OS X any more.

Thanks for your effort, but something is not right.
Configure detects that no ALSA is present, but still goes ahead and 
tries to compile an ALSA program:

checking for ALSA... no
configure: error: pkg-config found alsa, but it does not compile.  See 
config.log for error messages.

A sh -x on configure gives:

+ ALSA_REQUIRED=1.0.0
+ ALSA_MODULES='alsa >= 1.0.0'
+ pkg_failed=no
+ printf '%s\n' 'configure:9554: checking for ALSA'
+ printf %s 'checking for ALSA... '
+ test -n ''
+ test -n ''
+ pkg_failed=untried
+ test -n ''
+ test -n ''
+ pkg_failed=untried
+ test untried = yes
+ test untried = untried
+ printf '%s\n' 'configure:9613: result: no'
+ printf '%s\n' no
+ :
+ HAVE_ALSA=yes

So HAVE_ALSA becomes yes, even if it printed no on the line before.
Let me know if you need any more debugging help.

	Jan D.




  parent reply	other threads:[~2014-05-16 16:50 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
2014-05-16 15:52       ` Paul Eggert
2014-05-16 16:48         ` Glenn Morris
2014-05-16 16:50         ` Jan D. [this message]
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=537641EB.5000905@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@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 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).