Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/cargo: needs host-libxml2
Date: Mon, 10 Jun 2019 11:19:13 +0200	[thread overview]
Message-ID: <20190610091913.GA23106@ned> (raw)
In-Reply-To: <9adf69a9-b764-d5c5-e484-958bb9f8548f@mind.be>

Hi!

On 2019-06-10 01:07, Arnout Vandecappelle wrote:
>
>
> On 09/06/2019 23:08, Fabrice Fontaine wrote:
> > host-cargo needs host-libxml2 to avoid depending on an unworking
> > libxml2:
> >
> > --- stderr
> > cmake: /home/mark/buildroot-test/instance-1/output/host/lib/libcurl.so.4: no version information available (required by cmake)
> > cmake: symbol lookup error: /usr/lib/x86_64-linux-gnu/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP_60
> > thread 'main' panicked at '
> > command did not execute successfully, got: exit code: 127
>
>  I would like to understand this one a little more before blindly linking with
> host-libxml2...
>
>  I can't see anything in cargo's sources that refers to libxml2, except some of
> the vendored curl stuff, but those bits are only used on win32.

Same here. I tried to reproduce the issue in a chrooted Debian Stretch,
without success, even when adding libxml2-devel to the mix.

What is the configuration of the autobuilder?

Regards,

--
ELB

      reply	other threads:[~2019-06-10  9:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09 21:08 [Buildroot] [PATCH 1/1] package/cargo: needs host-libxml2 Fabrice Fontaine
2019-06-09 23:07 ` Arnout Vandecappelle
2019-06-10  9:19   ` Eric Le Bihan [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=20190610091913.GA23106@ned \
    --to=eric.le.bihan.dev@free.fr \
    --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