Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Pratik Farkase" <pratik.farkase@est.tech>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: "pratik.farkase@ericsson.com" <pratik.farkase@ericsson.com>
Subject: Re: [OE-core][PATCH v3] libffi: add ptest support
Date: Mon, 11 May 2026 14:25:17 +0200	[thread overview]
Message-ID: <DIFUGDKJKE7Y.SDTF3FXFC43W@bootlin.com> (raw)
In-Reply-To: <GV2P189MB3005B33FD42B8B07EF9ECC76FE382@GV2P189MB3005.EURP189.PROD.OUTLOOK.COM>

On Mon May 11, 2026 at 11:00 AM CEST, Pratik Farkase wrote:
> Hi Mathieu,
>
>   Thanks for looking into this.
>
>   The glib-2.0 locale issue looks pre-existing — my patch only modifies
>   ptest-packagelists.inc which likely invalidated sstate and exposed it.
>
>   The multilib symlinks conflict I can address in v4 if confirmed.
>
>   The complex_int failure on riscv64 could be arch-specific — happy to
>   exclude it if it reproduces consistently.
>
>   Let me know what you find after further testing.
>
> Best Regards,
> Pratik
>

So I tired again and applied this series on top of an otherwise fully
working branch. I basically got all the same failures:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/1577

This does include the ptest one, so I believe we should disable the
'libffi.complex/complex_int' test.

Thanks,
Mathieu

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



  reply	other threads:[~2026-05-11 12:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07  8:52 [OE-core][PATCH v1] libffi: add ptest support Pratik Farkase
2026-05-08 10:24 ` [OE-core][PATCH v2] " Pratik Farkase
2026-05-08 11:25   ` Marko, Peter
2026-05-08 11:38     ` Pratik Farkase
2026-05-08 11:36   ` [OE-core][PATCH v3] " Pratik Farkase
2026-05-11  6:09     ` Mathieu Dubois-Briand
2026-05-11  9:00       ` Pratik Farkase
2026-05-11 12:25         ` Mathieu Dubois-Briand [this message]
2026-05-12  8:30           ` Pratik Farkase
2026-05-12 15:16             ` Mathieu Dubois-Briand
2026-05-13  5:33               ` Mathieu Dubois-Briand
2026-05-13  8:27                 ` Pratik Farkase
2026-05-13 11:31                   ` Mathieu Dubois-Briand
2026-05-13 13:30                     ` Pratik Farkase
2026-05-13 13:27   ` [OE-core][PATCH v4] " Pratik Farkase
2026-05-20 16:02     ` Ross Burton
2026-05-21  8:30       ` Pratik Farkase
2026-05-25  9:30   ` [OE-core][PATCH v5] " Pratik Farkase

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=DIFUGDKJKE7Y.SDTF3FXFC43W@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pratik.farkase@ericsson.com \
    --cc=pratik.farkase@est.tech \
    /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