| Summary: | qt5webengine 5.12.2 build failed with arm toolchain and linaro toolchain | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | jacky lau <jacky> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | buildroot, marc.lamothe |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
jacky lau
2019-04-11 09:04:29 UTC
Hi, This could be related to kernel headers version used by the ARM toolchain [1]. Can you test with the Arm AArch64 toolchain 8.3-2019.03 recently updated ? Note, there are two different issues... I'm not sure about the second issue. [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b7d624ab431227af376787148cd7d474088c03aa Best regards, Romain Hello, For sure it's a bug related to -isystem` bug. It was fixed earlier but maybe something changed. https://github.com/buildroot/buildroot/commit/3a0ed5d25e26cb2ec99a1da077c9dcfea67b0ecc Removing -isystem <path> lines from ninja file when <path> is the path to your toolchain include dir make it works. But ninja files are generated. regards, Hi, It doesn't look like this but could it be related to pkgconf, which might be used to generate the Ninja files? We had to fix that [0] to get the correct -I and -isystem flags. Tom [0] http://lists.busybox.net/pipermail/buildroot/2019-October/261276.html (In reply to fazibear from comment #2) Today I hit this bug with buildroot master (37be55a5db) and this defconfig: BR2_TOOLCHAIN_BUILDROOT_GLIBC=y BR2_BINUTILS_VERSION_2_32_X=y BR2_GCC_VERSION_9_X=y BR2_TOOLCHAIN_BUILDROOT_CXX=y BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y BR2_PACKAGE_MESA3D=y BR2_PACKAGE_MESA3D_DRI_DRIVER_I965=y BR2_PACKAGE_MESA3D_OPENGL_GLX=y BR2_PACKAGE_MESA3D_OPENGL_EGL=y BR2_PACKAGE_QT5=y BR2_PACKAGE_QT5WEBENGINE=y BR2_PACKAGE_XORG7=y The 2019.05.x series is no longer supported, and qt5webengine has been bumped since, so closing the issue. Please reopen with more details if you still see the issue, thanks. |