mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/2] libxml2: update to 2.9.2
Date: Fri, 14 Nov 2014 16:01:37 +0100	[thread overview]
Message-ID: <4e98906a35da974f4cfbaff2ed43bd91@localhost> (raw)
In-Reply-To: <20141113165019.GR30196@pengutronix.de>

Hei hei, 

Am 2014-11-13 17:50, schrieb Michael Olbrich:
> host-libxml2 failed to build here. I'm not sure why. Some missing lzma
> symbols. Also, configure got some new options that should be added.

I have to admit I was not aware of host-libxslt and host-libxml2 and had
a look now which packages use them. I tried building with two different
toolchains after a `ptxdist clean` on different targets after activating
some packages using those host packages. Both did not fail:

OSELAS.Toolchain-2012.12.1/arm-v5te-linux-gnueabi
OSELAS.Toolchain-2013.12.2/arm-1136jfs-linux-gnueabihf

So I could not reproduce this (yet), but could try for two other
targets. Build machine is Debian 7 Wheezy on amd64 here.

Besides: I'll have a look into the changed options and resend a new
patch.

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-11-14 15:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 20:11 [ptxdist] update libxml2 and libxslt Alexander Dahl
2014-10-27 20:11 ` [ptxdist] [PATCH 1/2] libxslt: update to 1.1.28 Alexander Dahl
2014-11-13 16:49   ` Michael Olbrich
2014-10-27 20:11 ` [ptxdist] [PATCH 2/2] libxml2: update to 2.9.2 Alexander Dahl
2014-11-13 16:50   ` Michael Olbrich
2014-11-14 15:01     ` Alexander Dahl [this message]
2014-11-18 15:02     ` Alexander Dahl
2014-11-19 10:20       ` Michael Olbrich
2014-11-19 11:16         ` Alexander Dahl
2014-11-19 11:51           ` Michael Olbrich
2014-11-21  7:00             ` [ptxdist] [PATCH 1/2] " Alexander Dahl
2014-11-21  7:00               ` [ptxdist] [PATCH 2/2] libxml2: handle new ./configure options Alexander Dahl
2014-11-21 14:44                 ` Michael Olbrich
2014-11-24 11:25                   ` [ptxdist] [PATCHv3 0/2] libxml/libxslt update Alexander Dahl
2014-11-24 11:25                     ` [ptxdist] [PATCHv3 1/2] libxslt: add --without-python to host package Alexander Dahl
2014-11-24 11:25                     ` [ptxdist] [PATCHv3 2/2] libxml2: update to 2.9.2 Alexander Dahl
2014-11-26  9:58                     ` [ptxdist] [PATCHv3 0/2] libxml/libxslt update Michael Olbrich
2014-11-26 10:20                       ` Alexander Dahl
2014-11-26 15:24                         ` Michael Olbrich
2014-11-26 17:43                           ` [ptxdist] [PATCHv3 1/2] libxslt: add --without-python to host package Alexander Dahl
2014-11-26 17:43                             ` [ptxdist] [PATCHv3 2/2] libxml2: update to 2.9.2 Alexander Dahl
2014-11-27  8:59                               ` Michael Olbrich

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=4e98906a35da974f4cfbaff2ed43bd91@localhost \
    --to=post@lespocky.de \
    --cc=ptxdist@pengutronix.de \
    /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