Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14921] New: wpewebkit build fails because of internal build order
Date: Fri, 22 Jul 2022 10:24:17 +0000	[thread overview]
Message-ID: <bug-14921-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=14921

            Bug ID: 14921
           Summary: wpewebkit build fails because of internal build order
           Product: buildroot
           Version: 2022.02.3
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: buildroot@heine.tech
                CC: buildroot@uclibc.org
  Target Milestone: ---

Hi,

since wpewebkit was bumped to 2.36.x (which is the case for 2022.05 as well as
2022.02.3) the build fails with my config. This bug was already briefly
mentioned on the ML but I file it here for visibility.

This bug happens depending on the defconfig and the configuration of the
buildsystem (I'm building on a 24-core machine). When I restart the build it
succeeds because the missing dependency was then already build.

Two traces I recorded:

Scanning dependencies of target jsc
[ 39%] Building CXX object
Source/JavaScriptCore/shell/CMakeFiles/jsc.dir/__/jsc.cpp.o
[ 39%] Linking CXX executable ../../../bin/jsc
/builds/chp/bsp/buildroot/build/per-package/wpewebkit/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabihf/10.3.1/../../../../arm-none-linux-gnueabihf/bin/ld:
../CMakeFiles/JavaScriptCore.dir/__/__/JavaScriptCore/DerivedSources/unified-sources/UnifiedSource-6e4525b9-1.cpp.o:
in function `JSC::LLInt::CLoop::initialize()':
UnifiedSource-6e4525b9-1.cpp:(.text+0x2f4): undefined reference to
`JSC::LLInt::CLoop::execute(JSC::OpcodeID, void*, JSC::VM*,
JSC::ProtoCallFrame*, bool)'
/builds/chp/bsp/buildroot/build/per-package/wpewebkit/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabihf/10.3.1/../../../../arm-none-linux-gnueabihf/bin/ld:
../CMakeFiles/JavaScriptCore.dir/__/__/JavaScriptCore/DerivedSources/unified-sources/UnifiedSource-6e4525b9-1.cpp.o:
in function `vmEntryToJavaScript':
UnifiedSource-6e4525b9-1.cpp:(.text+0xb40): undefined reference to
`JSC::LLInt::CLoop::execute(JSC::OpcodeID, void*, JSC::VM*,
JSC::ProtoCallFrame*, bool)'
/builds/chp/bsp/buildroot/build/per-package/wpewebkit/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabihf/10.3.1/../../../../arm-none-linux-gnueabihf/bin/ld:
../CMakeFiles/JavaScriptCore.dir/__/__/JavaScriptCore/DerivedSources/unified-sources/UnifiedSource-6e4525b9-1.cpp.o:
in function `vmEntryToNative':
UnifiedSource-6e4525b9-1.cpp:(.text+0xbc0): undefined reference to
`JSC::LLInt::CLoop::execute(JSC::OpcodeID, void*, JSC::VM*,
JSC::ProtoCallFrame*, bool)'
collect2: error: ld returned 1 exit status


[ 39%] Built target JavaScriptCore_CopyPrivateHeaders
Scanning dependencies of target jsc
make[4]: *** No rule to make target
'Source/JavaScriptCore/CMakeFiles/LowLevelInterpreterLib.dir/llint/LowLevelInterpreter.cpp.o',
needed by 'bin/jsc'.  Stop.
make[4]: *** Waiting for unfinished jobs....
[ 39%] Building CXX object
Source/JavaScriptCore/shell/CMakeFiles/jsc.dir/__/jsc.cpp.o
make[3]: *** [CMakeFiles/Makefile2:775:
Source/JavaScriptCore/shell/CMakeFiles/jsc.dir/all] Error 2
make[3]: *** Waiting for unfinished jobs....
Scanning dependencies of target LowLevelInterpreterLib
[ 39%] Building CXX object
Source/JavaScriptCore/CMakeFiles/LowLevelInterpreterLib.dir/llint/LowLevelInterpreter.cpp.o
[ 39%] Built target LowLevelInterpreterLib
[ 39%] Built target WebInspectorUI
make[2]: *** [Makefile:152: all] Error 2
make[1]: *** [package/pkg-generic.mk:293:
/home/mheinemann/buildroot/build/build/wpewebkit-2.36.3/.stamp_built] Error 2
make: *** [Makefile:23: _all] Error 2


So it seems JSC is depending on LowLevelInterpreterLib which is built in
parallel and thus not (always) finished in time.

Defconfig with which I can reproduce this but it might depend on the system you
are building on:

BR2_LINUX_KERNEL_DEFCONFIG="bcm2711"
BR2_LINUX_KERNEL_DTS_SUPPORT=y
BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2711-rpi-4-b"
BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
BR2_PACKAGE_COG=y
BR2_PACKAGE_MESA3D=y
BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_V3D=y
BR2_PACKAGE_MESA3D_OPENGL_ES=y
BR2_PACKAGE_RPI_FIRMWARE=y
BR2_PACKAGE_RPI_FIRMWARE_VARIANT_PI4=y
BR2_PACKAGE_RPI_FIRMWARE_CONFIG_FILE="board/raspberrypi4/config_4.txt"
BR2_PACKAGE_WPEWEBKIT=y
BR2_TARGET_ROOTFS_EXT2=y
BR2_TARGET_ROOTFS_EXT2_4=y
BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
# BR2_TARGET_ROOTFS_TAR is not set
BR2_PACKAGE_HOST_DOSFSTOOLS=y
BR2_PACKAGE_HOST_GENIMAGE=y
BR2_PACKAGE_HOST_MTOOLS=y

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-07-22 10:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 10:24 bugzilla [this message]
2022-09-27  6:58 ` [Buildroot] [Bug 14921] wpewebkit build fails because of internal build order bugzilla

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=bug-14921-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox