From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/2] libxml2: update to 2.9.2
Date: Wed, 19 Nov 2014 11:20:45 +0100 [thread overview]
Message-ID: <20141119102045.GE16550@pengutronix.de> (raw)
In-Reply-To: <7bcb3fb43b6eb6d77ee1f6034a8ca043@localhost>
On Tue, Nov 18, 2014 at 04:02:22PM +0100, Alexander Dahl wrote:
> Am 2014-11-13 17:50, schrieb Michael Olbrich:
> > On Mon, Oct 27, 2014 at 09:11:09PM +0100, Alexander Dahl wrote:
> >> Also integrated two changes from upstream fixing two minor issues.
> >> Build successfully tested against all ptxdist packages requiring
> >> libxml2, no runtime tests.
> >>
> >
> > 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.
>
> --with-lzma is one of the new options. For ptxdist the liblzma lib is
> part of the package xz. For the host-libxml2 package this option is not
> set or unset, prepare stage aka ./configure contains this here:
>
> checking for LZMA... no
> checking lzma.h usability... no
> checking lzma.h presence... no
> checking for lzma.h... no
>
> Not sure if --without-lzma should be added to the host-libxml2.make
> rule? On my systems with different BSPs this was always handled
> automatically without errors.
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.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-11-19 10:20 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 [this message]
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=20141119102045.GE16550@pengutronix.de \
--to=m.olbrich@pengutronix.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