From: David Reitter <david.reitter@gmail.com>
To: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: build broken: libxml - i386 vs. X86_64 - configure problem
Date: Mon, 13 Sep 2010 10:30:54 -0400 [thread overview]
Message-ID: <2622DDFD-A026-430F-959B-167F6462D731@gmail.com> (raw)
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$ ./configure --with-ns
...
checking build system type... x86_64-apple-darwin10.4.0
checking host system type... x86_64-apple-darwin10.4.0
...
checking for libxml-2.0 > 2.2.0... yes
checking LIBXML2_CFLAGS... -I/opt/local/include/libxml2 -I/opt/local/include
checking LIBXML2_LIBS... -L/opt/local/lib -lxml2 -lpthread -lz -liconv -lm
...
gcc -prebind -framework AppKit -Xlinker -headerpad -Xlinker 6C8 \
-o temacs pre-crt0.o dispnew.o frame.o scroll.o xdisp.o menu.o window.o charset.o coding.o category.o ccl.o character.o chartab.o bidi.o cm.o term.o terminal.o xfaces.o emacs.o keyboard.o macros.o keymap.o sysdep.o buffer.o filelock.o insdel.o marker.o minibuf.o fileio.o dired.o filemode.o cmds.o casetab.o casefiddle.o indent.o search.o regex.o undo.o alloc.o data.o doc.o editfns.o callint.o eval.o floatfns.o fns.o font.o print.o lread.o syntax.o unexmacosx.o bytecode.o process.o callproc.o region-cache.o sound.o atimer.o doprnt.o strftime.o intervals.o textprop.o composite.o md5.o xml.o nsterm.o nsfns.o nsmenu.o nsselect.o nsimage.o nsfont.o fontset.o fringe.o image.o terminfo.o lastfile.o mktime.o -L/opt/local/lib -lxml2 -lpthread -lz -liconv -lm -lresolv -lncurses
ld: warning: in /opt/local/lib/libxml2.dylib, file is not of required architecture
Undefined symbols:
"_xmlCleanupParser", referenced from:
_parse_buffer in xml.o
"_xmlDocGetRootElement", referenced from:
_parse_buffer in xml.o
"_xmlReadMemory", referenced from:
_parse_buffer in xml.o
"_htmlReadMemory", referenced from:
_parse_buffer in xml.o
"_xmlCheckVersion", referenced from:
_parse_buffer in xml.o
"_xmlFreeDoc", referenced from:
_parse_buffer in xml.o
ld: symbol(s) not found
dr@elin:~/em24.git emacs24$ lipo -info /opt/local/lib/libxml2.dylib
Non-fat file: /opt/local/lib/libxml2.dylib is architecture: i386
Would it be possible to fix the configure script to make sure that the library is not only present, but that it can actually be bound?
next reply other threads:[~2010-09-13 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 14:30 David Reitter [this message]
2010-09-13 14:56 ` build broken: libxml - i386 vs. X86_64 - configure problem Lars Magne Ingebrigtsen
2010-09-13 17:51 ` Chad Brown
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
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=2622DDFD-A026-430F-959B-167F6462D731@gmail.com \
--to=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 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).