On Wed Jul 22, 2026 at 11:57 PM CEST, Khem Raj via lists.openembedded.org wrote:
> Switch the recipe from autotools to meson:
>
> - inherit meson instead of autotools; drop gettext (the meson build has
>   no i18n)
> - Map the PACKAGECONFIG knobs to meson options: --enable-runtime=X
>   becomes -Druntime=X, and builtin PSL data stays enabled via meson's
>   default (-Dbuiltin=true), matching the previous --enable-builtin.
> - Disable the bundled tests and fuzzers with -Dtests=false.
> - The gtk-doc class drives -Ddocs on its own via GTKDOC_MESON_OPTION.
>
> Unlike the autotools tarball, meson regenerates psl.1 at build time and
> stamps it with `date +%B %Y`, which is not reproducible. Backport the
> proposed upstream fix to honour SOURCE_DATE_EPOCH.
>
> Signed-off-by: Khem Raj <[email protected]>
> ---

Hi Khem,

> --- a/meta/recipes-support/libpsl/libpsl_0.23.0.bb
> +++ b/meta/recipes-support/libpsl/libpsl_0.23.0.bb
> @@ -12,15 +12,18 @@ LIC_FILES_CHKSUM = 
> "file://LICENSE;md5=49296c1806ef92c28297fb264163d81e \
>                      "
>
>  SRC_URI = "${GITHUB_BASE_URI}/download/${PV}/${BP}.tar.gz \
> +           file://0001-Support-reproducible-builds.patch \
>             "
>  SRC_URI[sha256sum] = 
> "f39b9631b3d369a21259ea4654f8875c0ec6995ce9551c0eb5d423e4c011f911"
>
>  GITHUB_BASE_URI = "https://github.com/rockdaboot/libpsl/releases";
>
> -inherit autotools gettext gtk-doc manpages pkgconfig lib_package 
> github-releases
> +inherit meson gtk-doc pkgconfig lib_package github-releases manpages
> +
> +# Do not build the bundled tests and fuzzers.
> +EXTRA_OEMESON = "-Dtests=false"
>
>  PACKAGECONFIG ?= "idn2"
> -PACKAGECONFIG[manpages] = "--enable-man,--disable-man,libxslt-native"

It looks like we have some user of this PACKAGECONFIG:

ERROR: libpsl-0.23.0-r0 do_configure: QA Issue: libpsl: invalid 
PACKAGECONFIG(s): manpages [invalid-packageconfig]
ERROR: libpsl-0.23.0-r0 do_configure: Fatal QA errors were found, failing task.

https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/4039

Looking at oe-core it's not obvious to me where it comes from, and why
we have this error. I also note I did not reproduce it locally on a
quick test, maybe we have to use a specific configuration.

Can you have a look at the issue?

Thanks,
Mathieu

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

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#241864): 
https://lists.openembedded.org/g/openembedded-core/message/241864
Mute This Topic: https://lists.openembedded.org/mt/120402099/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to