Branch: refs/heads/webkitglib/2.54
  Home:   https://github.com/WebKit/WebKit
  Commit: 8809525184e0790fb980ecd97edc7535cdc97433
      
https://github.com/WebKit/WebKit/commit/8809525184e0790fb980ecd97edc7535cdc97433
  Author: Nikolas Zimmermann <[email protected]>
  Date:   2026-08-28 (Fri, 28 Aug 2026)

  Changed paths:
    M Tools/yocto/meta-openembedded_and_meta-webkit.patch

  Log Message:
  -----------
  Cherry-pick 318819@main (18a9a4ac6188). 
https://bugs.webkit.org/show_bug.cgi?id=321337

    [WPE][cross-toolchain-helper] webkitdevci builds fail on hosts with glibc 
2.43 (e.g. Ubuntu 26.04 SDK)
    https://bugs.webkit.org/show_bug.cgi?id=321337

    Reviewed by Carlos Alberto Lopez Perez.

    The do_package task dies while copying a recipe's image directory:

        tar: ./usr/share: Cannot mkdir: Function not implemented

    pseudo 1.9.3, the revision pinned by poky scarthgap 5.0.18, wraps openat2()
    with an unconditional ENOSYS and hopes that callers fall back to an older
    syscall. GNU tar linked against glibc 2.43 calls openat2() and reports the
    error instead of falling back, so every do_package fails. tar is currently
    the only entry in tmp/hosttools that references openat2.

    Upstream pseudo implements the openat2() wrapper since 1.9.9, so bump the
    pseudo recipe to upstream master until poky ships a new enough revision.

    * Tools/yocto/meta-openembedded_and_meta-webkit.patch:

    Canonical link: https://commits.webkit.org/318819@main

Canonical link: https://commits.webkit.org/317695.161@webkitglib/2.54


  Commit: 47a50a065e358a670eb58c4ea5ea2f17849d71af
      
https://github.com/WebKit/WebKit/commit/47a50a065e358a670eb58c4ea5ea2f17849d71af
  Author: Nikolas Zimmermann <[email protected]>
  Date:   2026-08-28 (Fri, 28 Aug 2026)

  Changed paths:
    M Tools/yocto/rpi/local-rpi3-32bits-mesa.conf
    M Tools/yocto/rpi/local-rpi3-32bits-userland.conf
    M Tools/yocto/rpi/local-rpi3-64bits-mesa.conf
    M Tools/yocto/rpi/local-rpi4-32bits-mesa.conf
    M Tools/yocto/rpi/local-rpi4-64bits-mesa.conf

  Log Message:
  -----------
  Cherry-pick 319147@main (5863d45bdf1a). 
https://bugs.webkit.org/show_bug.cgi?id=321449

    [WPE][cross-toolchain-helper] serial-getty@ttyS0 restarts in a loop on the 
RPi bots
    https://bugs.webkit.org/show_bug.cgi?id=321449

    Reviewed by Carlos Alberto Lopez Perez.

    meta-raspberrypi defaults SERIAL_CONSOLES to the mini UART (ttyS0) and the 
image
    ships with [email protected] enabled. The firmware only powers up 
that
    port when enable_uart=1 is set in config.txt, which we never set, so agetty 
fails.
    However systemd will try to restart it every 10s, flooding the journal.

    Nobody attaches a serial cable to these machines, so stop installing the 
getty.

    * Tools/yocto/rpi/local-rpi3-32bits-mesa.conf:
    * Tools/yocto/rpi/local-rpi3-32bits-userland.conf:
    * Tools/yocto/rpi/local-rpi3-64bits-mesa.conf:
    * Tools/yocto/rpi/local-rpi4-32bits-mesa.conf:
    * Tools/yocto/rpi/local-rpi4-64bits-mesa.conf:

    Canonical link: https://commits.webkit.org/319147@main

Canonical link: https://commits.webkit.org/317695.162@webkitglib/2.54


  Commit: fa72fa4b7259d16276ff3fe79cc5110903c15fe6
      
https://github.com/WebKit/WebKit/commit/fa72fa4b7259d16276ff3fe79cc5110903c15fe6
  Author: Carlos Alberto Lopez Perez <[email protected]>
  Date:   2026-08-28 (Fri, 28 Aug 2026)

  Changed paths:
    M Tools/Scripts/build-webkit
    M Tools/Scripts/cross-toolchain-helper
    M Tools/Scripts/webkitdirs.pm
    M Tools/Scripts/webkitperl/BuildSubproject.pm
    A 
Tools/Scripts/webkitperl/webkitdirs_unittest/determineDefaultCompilerCMakeArgs.pl
    A 
Tools/Scripts/webkitperl/webkitdirs_unittest/determineDefaultCompilerClang.pl
    A 
Tools/Scripts/webkitperl/webkitdirs_unittest/determineDefaultCompilerCrossTarget.pl
    A 
Tools/Scripts/webkitperl/webkitdirs_unittest/determineDefaultCompilerNoClang.pl
    M Tools/glib/dependencies/apt
    M Tools/glib/dependencies/dnf
    M Tools/glib/dependencies/pacman
    M Tools/yocto/README.md

  Log Message:
  -----------
  Cherry-pick 319452@main (70e8323a4fdd). 
https://bugs.webkit.org/show_bug.cgi?id=321142

    [GTK][WPE] Use Clang by default when building with build-webkit
    https://bugs.webkit.org/show_bug.cgi?id=321142

    Reviewed by Carlos Garcia Campos.

    Until now the GTK and WPE ports were built with whatever compiler CMake
    picked up by default, which on Linux means GCC. This makes build-webkit
    and build-jsc use Clang instead for the GTK and WPE ports, and also for
    JSCOnly when building on Linux.

    This follows a recent change were we made Clang the default compiler on
    the CI. So this aligns the default developer build with the CI for the
    Linux ports. See 318539@main

    The compiler is selected by exporting CC and CXX rather than by passing
    -DCMAKE_C_COMPILER to CMake. The reason is that shouldRemoveCMakeCache()
    already keeps track of CC and CXX, so a change on the compiler removes
    the CMake cache and reconfigures the build directory. Note that this
    means that the first build after this change will reconfigure and
    rebuild any existing GTK, WPE or JSCOnly build directory.

    Both the clang and the clang++ binaries have to be available in the
    PATH. If any of them is missing then a warning is printed and the build
    continues using the default system compiler, so this doesn't break
    systems where Clang is not installed.

    Clang is also the new default for the cross-builds done with the
    toolchains generated by cross-toolchain-helper (the ones selected with
    the --cross-target flag). Those toolchains ship both compilers, and the
    environment setup script generated by cross-toolchain-helper already
    checks the value of CC and CXX to decide which one of the two to use, so
    in that case CC and CXX are set simply as a hint for that script and the
    binaries from the host PATH are not checked (the compiler used is the
    cross-compiled one from the toolchain). When the toolchain has no Clang
    support the setup script keeps using GCC as before.

    Anyone can still choose a different compiler: setting CC and CXX in the
    environment or passing the compiler via --cmakeargs takes precedence over
    the default.

    * Tools/Scripts/build-webkit:
    * Tools/Scripts/cross-toolchain-helper:
    (YoctoCrossBuilder.cross_dev_shell):
    * Tools/Scripts/webkitdirs.pm:
    (determineDefaultCompiler):
    (buildCMakeProjectOrExit):
    * Tools/Scripts/webkitperl/BuildSubproject.pm:
    * 
Tools/Scripts/webkitperl/webkitdirs_unittest/determineDefaultCompilerCMakeArgs.pl:
 Added.
    * 
Tools/Scripts/webkitperl/webkitdirs_unittest/determineDefaultCompilerClang.pl: 
Added.
    * 
Tools/Scripts/webkitperl/webkitdirs_unittest/determineDefaultCompilerCrossTarget.pl:
 Added.
    * 
Tools/Scripts/webkitperl/webkitdirs_unittest/determineDefaultCompilerNoClang.pl:
 Added.
    * Tools/glib/dependencies/apt:
    * Tools/glib/dependencies/dnf:
    * Tools/glib/dependencies/pacman:
    * Tools/yocto/README.md:

    Canonical link: https://commits.webkit.org/319452@main

Canonical link: https://commits.webkit.org/317695.163@webkitglib/2.54


Compare: https://github.com/WebKit/WebKit/compare/71f1a82c16c4...fa72fa4b7259

To unsubscribe from these emails, change your notification settings at 
https://github.com/WebKit/WebKit/settings/notifications

Reply via email to