From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 17438@debbugs.gnu.org
Subject: bug#17438: xrandr linking problem on OS X
Date: Sun, 11 May 2014 13:58:15 -0400 [thread overview]
Message-ID: <2c7g5skxjc.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <536EEA53.7020605@cs.ucla.edu> (Paul Eggert's message of "Sat, 10 May 2014 20:11:15 -0700")
Paul Eggert wrote:
>> Does configure.ac really need to require this version of pkg-config, or just autogen.sh?
>
> If the xrandr configuration is failing due to a bug in older
> pkg-config versions, this suggests that configure.ac really needs the
> newer pkg-config.
But it's not failing in that way in the emacs-24 branch on hydra, which
also uses pkg-config 0.23. So the problem is in pkg.m4 that older
pkg-config supply, not the pkg-config program.
I think it's that they don't do the equivalent of
--exists && --cflags && --libs
https://bugs.freedesktop.org/show_bug.cgi?id=29801
> I suppose we could go back to the emacs-24 way of doing things, and
> use or own PKG_CHECK_MODULES macro.
I think this is equivalent to my suggestion of copying pkg.m4 from a
recent pkg-config into our m4 directory.
But assuming we can get a newer pkg-config on hydra, I think it would be
fine to require >= 0.26 in autogen.sh, and leave configure.ac alone.
next prev parent reply other threads:[~2014-05-11 17:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 20:22 bug#17438: xrandr linking problem on OS X Glenn Morris
2014-05-08 20:35 ` Glenn Morris
2014-05-08 20:45 ` Glenn Morris
2014-05-08 22:00 ` Glenn Morris
2014-05-09 6:44 ` Eli Zaretskii
2014-05-09 6:50 ` Glenn Morris
2014-05-11 2:30 ` Paul Eggert
2014-05-11 2:34 ` Glenn Morris
2014-05-11 3:11 ` Paul Eggert
2014-05-11 17:58 ` Glenn Morris [this message]
2014-05-11 18:12 ` Eli Zaretskii
2014-05-11 18:15 ` Glenn Morris
2014-05-11 18:21 ` Eli Zaretskii
2014-05-11 19:15 ` Paul Eggert
2014-05-12 5:26 ` Katsumi Yamaoka
2014-05-12 6:11 ` Paul Eggert
2014-05-12 23:37 ` Glenn Morris
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=2c7g5skxjc.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=17438@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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.