From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] meson: move libmpathpersist test
Date: Thu, 17 Sep 2020 11:59:41 +0200 [thread overview]
Message-ID: <879a2c0f-7015-2865-9488-b0d5cb6d07aa@redhat.com> (raw)
In-Reply-To: <20200916162621.100141-1-pbonzini@redhat.com>
On 16/09/2020 18.26, Paolo Bonzini wrote:
> Move the libmpathpersist test, as well as its dependency
> libudev, to meson. This should fix or help debugging
> https://travis-ci.com/github/huth/qemu/jobs/385737549#L4528
Thanks, this indeed decreased the amount of linker errors after I
applied the patches, but there are still two errors left:
https://travis-ci.com/github/huth/qemu/jobs/385871016#L7839
Any ideas?
Thomas
next prev parent reply other threads:[~2020-09-17 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 16:26 [PATCH 0/2] meson: move libmpathpersist test Paolo Bonzini
2020-09-16 16:26 ` [PATCH 1/2] meson: move libudev test Paolo Bonzini
2020-09-16 16:26 ` [PATCH 2/2] meson: move libmpathpersist test Paolo Bonzini
2020-09-16 17:09 ` Thomas Huth
2020-09-16 17:17 ` Paolo Bonzini
2020-09-17 9:59 ` Thomas Huth [this message]
2020-09-17 10:36 ` [PATCH 0/2] " Paolo Bonzini
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=879a2c0f-7015-2865-9488-b0d5cb6d07aa@redhat.com \
--to=thuth@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).