From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gettext: host variant needs host-libxml2
Date: Tue, 29 Dec 2015 13:56:43 -0300 [thread overview]
Message-ID: <5682BB4B.1060805@zacarias.com.ar> (raw)
In-Reply-To: <1451165734-15534-1-git-send-email-yann.morin.1998@free.fr>
On 26/12/15 18:35, Yann E. MORIN wrote:
> From: Ignacy Gaw?dzki <ignacy.gawedzki@green-communications.fr>
>
> Of host-gettext, we only build the tools. however some of those tools
> have a --color option, which needs libxml2.
>
> If the libxml2 development files are missing on the host, a bundled
> subset of libxml2 is used, and all seems OK. But if they ar epresent,
> then the host libxml2 is used. On some distros, lbxml2 is linked with
> liblzma. And if we happend to _then_ build our host-liblzma, we may have
> a conflict later when trying to run any of the host-gettext tools.
>
> Always build host-gettext with our own host-libxml2 which is not linked
> with liblzma.
>
> Fixes https://bugs.busybox.net/show_bug.cgi?id=7886
>
> Signed-off-by: Ignacy Gaw?dzki <ignacy.gawedzki@green-communications.fr>
> [nicolas: added extended commit message]
> Signed-off-by: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>
> [yann.morin.1998 at free.fr: rebase; add comment; enhance commit log]
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Regards.
prev parent reply other threads:[~2015-12-29 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 21:35 [Buildroot] [PATCH] package/gettext: host variant needs host-libxml2 Yann E. MORIN
2015-12-27 10:44 ` Thomas Petazzoni
2015-12-27 10:54 ` Yann E. MORIN
2015-12-27 11:22 ` Thomas Petazzoni
2015-12-29 16:56 ` Thomas Petazzoni
2015-12-29 16:56 ` Gustavo Zacarias [this message]
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=5682BB4B.1060805@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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 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.