All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
	mingli.yu@eng.windriver.com,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] lttng-tools: Upgrade 2.13.15 -> 2.14.0
Date: Thu, 17 Jul 2025 17:51:22 +0800	[thread overview]
Message-ID: <5d5cbde0-eaad-461b-b878-cbd1411352cc@windriver.com> (raw)
In-Reply-To: <DBE8DHTVEB13.27BZ3GL6DGZ1Z@bootlin.com>



On 7/17/25 17:42, Mathieu Dubois-Briand wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
> 
> On Thu Jul 17, 2025 at 10:22 AM CEST, Mingli via lists.openembedded.org Yu wrote:
>> From: Mingli Yu <mingli.yu@windriver.com>
>>
>> Remove 3 backported patch.
>> 0001-Fix-rotation-destroy-flush-fix-session-daemon-abort-.patch
>> 0001-compat-Define-off64_t-as-off_t-on-linux.patch
>> 0001-tests-add-check_skip_kernel_test-to-check-root-user-.patch
>>
>> Remove 0001-fix-lttng-tools-fails-to-compile-with-libxml2-2.14.0.patch
>> as the the issue has been fixed in another way as [1]
>>
>> Rebase 0001-tests-do-not-strip-a-helper-library.patch and disable-tests.patch
>> to fuzz issue.
>>
>> Add babeltrace2 to DEPENDS to fix below configure error.
>>   | configure: error: libbabeltrace2 is required to build tests
>>
>> src/common/config/session.xsd is restructured to src/common/session.xsd [2]
>>
>> Add 0001-gen-ust-events-constructor-change-rpath-to-libdir-li.patch to fix
>> the below buildpath QA issue.
>> ERROR: lttng-tools-2.14.0-r0 do_package_qa: QA Issue: File /usr/lib/lttng-tools/ptest/tests/utils/testapp/gen-ust-events-constructor/gen-ust-events-c-constructor-so in package lttng-tools-ptest contains reference to TMPDIR [buildpaths]
>> ERROR: lttng-tools-2.14.0-r0 do_package_qa: QA Issue: lttng-tools-ptest: /usr/lib/lttng-tools/ptest/tests/utils/testapp/gen-ust-events-constructor/gen-ust-events-c-constructor-so contains bad RPATH /buildarea3/myu2/yocto/builds/ptest-2025-07-09/tmp/work/core2-64-poky-linux/lttng-tools/2.14.0/build/tests/utils/testapp/gen-ust-events-constructor [rpaths]
>> ERROR: lttng-tools-2.14.0-r0 do_package_qa: QA Issue: File /usr/lib/lttng-tools/ptest/tests/utils/testapp/gen-ust-events-constructor/gen-ust-events-constructor-so in package lttng-tools-ptest contains reference to TMPDIR [buildpaths]
>> ERROR: lttng-tools-2.14.0-r0 do_package_qa: QA Issue: lttng-tools-ptest: /usr/lib/lttng-tools/ptest/tests/utils/testapp/gen-ust-events-constructor/gen-ust-events-constructor-so contains bad RPATH /buildarea3/myu2/yocto/builds/ptest-2025-07-09/tmp/work/core2-64-poky-linux/lttng-tools/2.14.0/build/tests/utils/testapp/gen-ust-events-constructor [rpaths]
>>
>> [1] https://github.com/lttng/lttng-tools/commit/2d2e77ddc9e3e63c3c658e824fb754f5a534a6ab
>> [2] https://github.com/lttng/lttng-tools/commit/4ae042345b4094e98611744d9ba6c92265058fdb
>>
>> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
>> ---
> 
> Hi Mingli,
> 
> Thanks for your patch.
> 
> It looks like this is breaking when using musl:
> 
> ERROR: lttng-tools-2.14.0-r0 do_compile: oe_runmake failed
> ...
> | ../../../sources/lttng-tools-2.14.0/src/common/eventfd.cpp: In lambda function:
> | ../../../sources/lttng-tools-2.14.0/src/common/eventfd.cpp:18:31: error: expected id-expression before numeric constant
> |    18 |                 int flags = ::EFD_CLOEXEC;
> |       |                               ^~~~~~~~~~~
> | ../../../sources/lttng-tools-2.14.0/src/common/eventfd.cpp:21:36: error: expected id-expression before numeric constant
> |    21 |                         flags |= ::EFD_SEMAPHORE;
> |       |                                    ^~~~~~~~~~~~~
> 
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/111/builds/790
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/2072
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/3/builds/2102
> 
> Can you have a look at these fails please?

Okay, I will look into this and send v2 then.

Thanks,
Mingli

> 
> --
> Mathieu Dubois-Briand, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
> 


      reply	other threads:[~2025-07-17  9:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-17  8:22 [PATCH 1/2] lttng-ust: Upgrade 2.13.9 -> 2.14.0 mingli.yu
2025-07-17  8:22 ` [PATCH 2/2] lttng-tools: Upgrade 2.13.15 " mingli.yu
2025-07-17  9:42   ` [OE-core] " Mathieu Dubois-Briand
2025-07-17  9:51     ` Yu, Mingli [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=5d5cbde0-eaad-461b-b878-cbd1411352cc@windriver.com \
    --to=mingli.yu@windriver.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=mingli.yu@eng.windriver.com \
    --cc=openembedded-core@lists.openembedded.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 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.