all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chad Brown <yandros@MIT.EDU>
To: David Reitter <david.reitter@gmail.com>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: build broken: libxml - i386 vs. X86_64 - configure problem
Date: Mon, 13 Sep 2010 10:51:13 -0700	[thread overview]
Message-ID: <89EF9F06-CF3D-45D6-8786-55FB77AD2EC2@mit.edu> (raw)
In-Reply-To: <2622DDFD-A026-430F-959B-167F6462D731@gmail.com>


On Sep 13, 2010, at 7:30 AM, David Reitter wrote:

> The libxml bindings or something else related to XML broke the build for me (on a mac), due to the chosen build architecture being 64-bit (chosen by default, and that is correct), but the library being i386:
> 
> dr@elin:~/em24.git emacs24$ lipo -info /opt/local/lib/libxml2.dylib
> Non-fat file: /opt/local/lib/libxml2.dylib is architecture: i386


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 

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?

*Chad


  parent reply	other threads:[~2010-09-13 17:51 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 [this message]
2010-09-13 18:06   ` David Reitter
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=89EF9F06-CF3D-45D6-8786-55FB77AD2EC2@mit.edu \
    --to=yandros@mit.edu \
    --cc=david.reitter@gmail.com \
    --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 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.