From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/xmlstarlet: fix host build
Date: Thu, 31 Aug 2017 09:39:21 +0200 [thread overview]
Message-ID: <20170831093921.11448124@windsurf.lan> (raw)
In-Reply-To: <CANLo3Jix+ojJWq6QTRaxxpOMDHBJtkUkiZnAzy6neY95h=OGCA@mail.gmail.com>
Hello,
Your e-mail is badly quoted. What happened?
On Thu, 31 Aug 2017 09:25:16 +0200, Romain Naour wrote:
> It would be nice to use LANG=C when building and copy/pasting error
> messages, to avoid French words in the middle :)
>
> "No such file or directory" looks english to me at 0h40 :p
But "erreur fatale" doesn't look very english, even at 0h40 :-)
> I had the issue locally, I think libxml-dev is installed on autobuilders.
> I was trying to reproduce the kodi build issue with glibc 2.26.
I'd be good to understand a little bit better what's happening. My
autobuilder definitely doesn't have libxml-dev installed:
$ dpkg -l | grep libxml
ii libxml2:amd64 2.8.0+dfsg1-7+wheezy8 amd64 GNOME XML library
I think it could actually be the opposite: you have libxml-dev
installed locally, and therefore the system-wide libxml installation
gets picked up, instead of the libxml built by Buildroot in
$(HOST_DIR). Could you verify this by checking if you have libxml-dev
installed on your system, reproducing the issue, then see what happens
when you uninstall libxml-dev ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-08-31 7:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 22:40 [Buildroot] [PATCH] package/xmlstarlet: fix host build Romain Naour
2017-08-31 7:14 ` Thomas Petazzoni
2017-08-31 7:25 ` Romain Naour
2017-08-31 7:39 ` Thomas Petazzoni [this message]
2017-08-31 10:51 ` Romain Naour
2017-08-31 11:10 ` Thomas Petazzoni
2017-08-31 18:42 ` Romain Naour
2017-08-31 19:33 ` Thomas Petazzoni
2017-09-01 19:36 ` Romain Naour
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=20170831093921.11448124@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox