public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Doug Hunley <doug.hunley@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fix for getting libxml2 compiled!
Date: Thu, 6 Sep 2012 10:56:20 -0400	[thread overview]
Message-ID: <CALxYTP5bFtb6pP=tEJ_-UCv0fBmt0S4Q4QnaPK3fNUPwk3xMrA@mail.gmail.com> (raw)
In-Reply-To: <trinity-125bf169-25a6-404f-9364-2b64d110f804-1346881372903@3capp-webde-bs38>

On Wed, Sep 5, 2012 at 5:42 PM, "Roland Häder" <r.haeder@web.de> wrote:
> Hi all,
>
> I finally got libxml2 compiled, first I had to do this:
>
> # emerge expat
> # emerge python
> # cd /usr/portage/dev-lang/python/
> # emerge python-2.7.3-r2.ebuild
> # cd -
>
> This makes sure that libexpat is there. Now the package is still not compiling because of a missing .so file, see this:
>
> # cd /usr/lib/python2.7/xml/parsers/
> # ln -sf /usr/lib/python2.7/site-packages/_xmlplus/parsers/pyexpat.so .
>
> If I don't do this a python script in /var/tmp/portage/dev-libs/libxml2-2.8.0_rc1/work/libxml2-2.8.0/python-2.7/ called generate.py (you have to call this python2.7 ./generate.py) will fail.
>
> Hope this saves someones endless hours.
>
> Regards,
>   Roland
>
> PS: There are a lot warnings compiling libxml2, you may want to fix them.
>
> I have used this to build libxml2: (temporary)
> USE="-ipv6 readline -debug -doc -examples -icu lzma python -static-libs -test"
>

Weird, I'm on 2.8.0-r1 and didn't have to do any hoop jumping to get
there (~amd64).

-- 
Douglas J Hunley (doug.hunley@gmail.com)
Twitter: @hunleyd                                               Web:
douglasjhunley.com
G+: http://goo.gl/sajR3


  reply	other threads:[~2012-09-06 15:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05 21:42 [gentoo-user] Fix for getting libxml2 compiled! "Roland Häder"
2012-09-06 14:56 ` Doug Hunley [this message]
2012-09-06 15:32   ` Aw: " "Roland Häder"
2012-09-07 18:04     ` Doug Hunley

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='CALxYTP5bFtb6pP=tEJ_-UCv0fBmt0S4Q4QnaPK3fNUPwk3xMrA@mail.gmail.com' \
    --to=doug.hunley@gmail.com \
    --cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox