From: Petri Latvala <petri.latvala@intel.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>,
igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] meson: Explicitly require libcurl for chamelium
Date: Thu, 9 May 2019 14:05:21 +0300 [thread overview]
Message-ID: <20190509110521.GI22949@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20190509105821.GH22949@platvala-desk.ger.corp.intel.com>
On Thu, May 09, 2019 at 01:58:21PM +0300, Petri Latvala wrote:
> On Thu, May 09, 2019 at 10:56:00AM +0300, Arkadiusz Hiler wrote:
> > Chamelium uses xmlrpc client which:
> >
> > $ xmlrpc-c-config client --libs
> > -L/usr/lib/x86_64-linux-gnu -lxmlrpc_client -lxmlrpc -lxmlrpc_xmlparse -lxmlrpc_xmltok -lxmlrpc_util -lcurl
> >
> > Debian/Ubuntu (and perhaps others) lack dependency on libcurl-dev:
> >
> > $ apt depends libxmlrpc-core-c3-dev
> > Depends: libxmlrpc-core-c3 (= 1.33.14-4)
> > Suggests: xmlrpc-api-utils
> >
> > $ apt depends libxmlrpc-core-c3
> > libxmlrpc-core-c3
> > Depends: libc6 (>= 2.14)
> > Depends: libcurl3 (>= 7.16.2)
>
> I don't see us installing libcurl-dev explicitly in gitlab-CI. Does
> kms_chamelium build there properly?
Apparently I was blind, in addition to only searching for libcurl-dev.
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-05-09 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 7:56 [igt-dev] [PATCH i-g-t] meson: Explicitly require libcurl for chamelium Arkadiusz Hiler
2019-05-09 8:01 ` Daniel Vetter
2019-05-09 10:58 ` Petri Latvala
2019-05-09 11:05 ` Petri Latvala [this message]
2019-05-09 11:01 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-05-09 13:41 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=20190509110521.GI22949@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=arkadiusz.hiler@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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