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: Wed, 19 Nov 2014 12:16:05 +0100	[thread overview]
Message-ID: <2e4dd0904364dc1decaac4fd2790eac6@localhost> (raw)
In-Reply-To: <20141119102045.GE16550@pengutronix.de>

Hei Michael, 

Am 2014-11-19 11:20, schrieb Michael Olbrich:
> This is probably why I get the error. I don't have the logs right now but
> I guess lzma was detected for me and something went wrong during linking.
> 
> This is why the rules should specify the configure options for all
> auto detected features.

But this is not the case for host-libxml2.make. I had a look into the
revision log. Last five changes on this file were made by you, one in
2014, one in 2012, three in 2010, everything else is much older.
HOST_LIBXML2 is selected by HOST_LIBXSLT only. HOST_LIBXSLT on the other
hand is selected by UDISKS, DEVICEKIT_DISKS, HOST_LIBXCB, and LIBXCB.
I'm not familiar with any of those and I'm not using any of those, so I
have no idea why HOST_LIBXSLT is needed and what would be reasonable
defaults for host libxslt and host libxml2 packages. :-/

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-19 11:16 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
2014-11-18 15:02     ` Alexander Dahl
2014-11-19 10:20       ` Michael Olbrich
2014-11-19 11:16         ` Alexander Dahl [this message]
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=2e4dd0904364dc1decaac4fd2790eac6@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