From: David Reitter <david.reitter@gmail.com>
To: Chad Brown <yandros@MIT.EDU>, Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: build broken: libxml - i386 vs. X86_64 - configure problem
Date: Mon, 13 Sep 2010 14:06:04 -0400 [thread overview]
Message-ID: <0A4044B9-65CB-4515-8B84-CF448E2CE05A@gmail.com> (raw)
In-Reply-To: <89EF9F06-CF3D-45D6-8786-55FB77AD2EC2@mit.edu>
On Sep 13, 2010, at 1:51 PM, Chad Brown wrote:
>
> Do you not have an libxml2 in /usr/lib?
>
> ; lipo -info /usr/lib/libxml2.dylib
> Architectures in the fat file: /usr/lib/libxml2.dylib are: x86_64 i386 ppc7400
Yes, I have the same, and yes, it appears shadowed.
> It looks like you've shadowed a useable library with something from Fink or MacPorts, at a guess. Perhaps setting PKG_CONFIG_PATH to something with /usr/lib/pkgconfig early will help?
PKG_CONFIG is indeed /opt/local/bin/pkg-config in my config.status.
Err, this is not the right way:
./configure --with-pkg-config-prog=/usr/lib/pkgconfig/
checking for pkg-config... (cached) /usr/lib/pkgconfig
./configure: line 11131: /usr/lib/pkgconfig: is a directory
*** Your version of pkg-config is too old. You need version 0.9.0 or newer.
*** See http://www.freedesktop.org/software/pkgconfig
I don't have another pkg-config binary than the one provided by macports.
PS.: Lars, consider updating "configure" in the branch after the change to "configure.in"
next prev parent reply other threads:[~2010-09-13 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 14:30 build broken: libxml - i386 vs. X86_64 - configure problem David Reitter
2010-09-13 14:56 ` Lars Magne Ingebrigtsen
2010-09-13 17:51 ` Chad Brown
2010-09-13 18:06 ` David Reitter [this message]
2010-09-13 18:08 ` Lars Magne Ingebrigtsen
2010-09-13 18:34 ` David Reitter
2010-09-13 18:40 ` Lars Magne Ingebrigtsen
2010-09-13 18:48 ` Lars Magne Ingebrigtsen
2010-09-13 19:31 ` David Reitter
2010-09-13 19:47 ` Lars Magne Ingebrigtsen
2010-09-13 20:23 ` Andreas Schwab
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=0A4044B9-65CB-4515-8B84-CF448E2CE05A@gmail.com \
--to=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=yandros@MIT.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 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).