From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: David Reitter <david.reitter@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: build broken: libxml - i386 vs. X86_64 - configure problem
Date: Mon, 13 Sep 2010 20:48:32 +0200 [thread overview]
Message-ID: <m3sk1dtr7j.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <65EE3DC2-0C2F-4469-ACBA-F4C633C5EB08@gmail.com>
David Reitter <david.reitter@gmail.com> writes:
> gcc -o conftest -g -O2 conftest.c -lxml2
Does the following patch fix it for you?
=== modified file 'configure.in'
*** configure.in 2010-09-13 14:58:48 +0000
--- configure.in 2010-09-13 18:45:28 +0000
***************
*** 2541,2546 ****
--- 2541,2547 ----
### I'm not sure what the version number should be, so I just guessed.
PKG_CHECK_MODULES(LIBXML2, libxml-2.0 > 2.2.0, HAVE_LIBXML2=yes, HAVE_LIBXML2=no)
if test "${HAVE_LIBXML2}" = "yes"; then
+ LIBS="$LIBXML2_LIBS $LIBS"
AC_CHECK_LIB(xml2, htmlReadMemory, HAVE_LIBXML2=yes, HAVE_LIBXML2=no)
if test "${HAVE_LIBXML2}" = "yes"; then
AC_DEFINE(HAVE_LIBXML2, 1, [Define to 1 if you have the libxml library (-lxml2).])
Emacs devel people, is that the correct incantation to add the LIBS
discovered by the PKG_CHECK_MODULES magic?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-09-13 18:48 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
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 [this message]
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=m3sk1dtr7j.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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.