From: Nathan Lynch <nathan_lynch@mentor.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/3] lttng-tools: update to 2.9.5
Date: Fri, 7 Jul 2017 14:46:25 -0500 [thread overview]
Message-ID: <87y3s0xc6m.fsf@mentor.com> (raw)
In-Reply-To: <CAJTo0La9rcpY8oxxuaWspjLM6NjJNugVopmdVEvps=sH2fMkcA@mail.gmail.com>
"Burton, Ross" <ross.burton@intel.com> writes:
> On 16 June 2017 at 22:39, Nathan Lynch <nathan_lynch@mentor.com> wrote:
>
>> Miscellaneous fixes.
>>
>
> This isn't related to the upgrade as it was a problem in the old release
> too but I thought you should know:
>
> WARNING: lttng-tools-2.9.5-r0 do_package_qa: QA Issue: lttng-tools-ptest:
> /usr/lib/lttng-tools/ptest/tests/regression/tools/health/health_check looks
> like a libtool wrapper script [libtool-wrapper]
> WARNING: lttng-tools-2.9.5-r0 do_package_qa: QA Issue: lttng-tools-ptest:
> /usr/lib/lttng-tools/ptest/tests/regression/tools/health/health_check looks
> like a libtool wrapper script [libtool-wrapper]
> WARNING: lttng-tools-2.9.5-r0 do_package_qa: QA Issue: lttng-tools-ptest:
> /usr/lib/lttng-tools/ptest/tests/regression/tools/live/live_test looks like
> a libtool wrapper script [libtool-wrapper]
> WARNING: lttng-tools-2.9.5-r0 do_package_qa: QA Issue: lttng-tools-ptest:
> /usr/lib/lttng-tools/ptest/tests/regression/tools/live/live_test looks like
> a libtool wrapper script [libtool-wrapper]
> WARNING: lttng-tools-2.9.5-r0 do_package_qa: QA Issue: lttng-tools-ptest:
> /usr/lib/lttng-tools/ptest/tests/unit/ini_config/ini_config looks like a
> libtool wrapper script [libtool-wrapper]
> WARNING: lttng-tools-2.9.5-r0 do_package_qa: QA Issue: lttng-tools-ptest:
> /usr/lib/lttng-tools/ptest/tests/unit/ini_config/ini_config looks like a
> libtool wrapper script [libtool-wrapper]
Where can I find the libtool-wrapper QA check? It doesn't appear to be
in oe-core or poky.
next prev parent reply other threads:[~2017-07-07 19:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 21:39 [PATCH 0/3] LTTng updates Nathan Lynch
2017-06-16 21:39 ` [PATCH 1/3] lttng-ust: update to 2.9.1 Nathan Lynch
2017-06-16 21:39 ` [PATCH 2/3] lttng-tools: update to 2.9.5 Nathan Lynch
2017-06-22 16:25 ` Burton, Ross
2017-06-22 21:28 ` Nathan Lynch
2017-07-07 19:46 ` Nathan Lynch [this message]
2017-07-07 19:50 ` Burton, Ross
2017-06-16 21:39 ` [PATCH 3/3] lttng-modules: update to 2.9.3 Nathan Lynch
2017-06-16 21:48 ` [PATCH v2 " Nathan Lynch
2017-06-16 22:01 ` ✗ patchtest: failure for LTTng updates 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=87y3s0xc6m.fsf@mentor.com \
--to=nathan_lynch@mentor.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.