Summary: | dev-qt/qtwebengine-6.6.1 failed to emerge: host/flatc failed with exit code -11 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Leonid Kopylov <leonchik1976> |
Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gyakovlev, ionen, leio |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=920555 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log.xz |
Description
Leonid Kopylov
2023-12-23 13:30:09 UTC
Created attachment 880257 [details]
build.log.xz
[3512/29761] /var/tmp/portage/dev-qt/qtwebengine-6.6.1/temp/python3.11/bin/python3 ../../../../../qtwebengine-everywhere-src-6.6.1/src/3rdparty/chromium/build/gn_run_binary.py host/flatc -c --keep-prefix -o gen/components/url_pattern_index/flat -I ../../../../../qtwebengine-everywhere-src-6.6.1/src/3rdparty/chromium/ ../../../../../qtwebengine-everywhere-src-6.6.1/src/3rdparty/chromium/components/url_pattern_index/flat/url_pattern_index.fbs [31mFAILED: [0mgen/components/url_pattern_index/flat/url_pattern_index_generated.h /var/tmp/portage/dev-qt/qtwebengine-6.6.1/temp/python3.11/bin/python3 ../../../../../qtwebengine-everywhere-src-6.6.1/src/3rdparty/chromium/build/gn_run_binary.py host/flatc -c --keep-prefix -o gen/components/url_pattern_index/flat -I ../../../../../qtwebengine-everywhere-src-6.6.1/src/3rdparty/chromium/ ../../../../../qtwebengine-everywhere-src-6.6.1/src/3rdparty/chromium/components/url_pattern_index/flat/url_pattern_index.fbs host/flatc failed with exit code -11 Likely a segfault. Could you try without -march=native? (aka just minimal CFLAGS=-O2 CXXFLAGS=-O2). It is failing on a different part, but maybe it's related to bug #920555. Then again, not sure if this -march=native is even doing anything due to another gcc bug. I do bet clang would work. (In reply to Ionen Wolkens from comment #3) > Then again, not sure if this -march=native is even doing anything due to > another gcc bug. I do bet clang would work. Depending on how broken things are (if these issues keep happening), I guess a USE=clang that's forced on arm64 could be something to consider. But if it's just -march issues, I could filter it. fwiw, the -march issue referenced about it not doing anything should only be an issue on Apple silicon (Apple M1, Apple M2, and Apple M3 once that boot too with Asahi Linux). Or other ARM64 that GCC doesn't detect or know about at all, but I don't know any others so far. About clang, *if* dropping -march with gcc did not help (check your new build.log to be sure it wasn't used), could you try it? Just a simple `CC=clang CXX=clang++ emerge -1 qtwebengine:6` should be enough. clang is more tested for chromium and already been confirmed to build qtwebengine:6 fine on arm64, albeit I'd rather avoid forcing it if possible. (In reply to Mart Raudsepp from comment #5) > fwiw, the -march issue [...] Thanks for clarifying, I guess segfaults could be -march related here too then. (In reply to Ionen Wolkens from comment #3) > Likely a segfault. > > Could you try without -march=native? (aka just minimal CFLAGS=-O2 > CXXFLAGS=-O2). It is failing on a different part, but maybe it's related to > bug #920555. > > Then again, not sure if this -march=native is even doing anything due to > another gcc bug. I do bet clang would work. without -march=native it builds successfully (In reply to Leonid Kopylov from comment #7) > without -march=native it builds successfully Thanks, guess time to filter out in the ebuild for arm64 when gcc is used then -- can revisit eventually. Seeing how it failed in a different location than the other bug (different repo, not v8's -- albeit it may still share some copy/pasted code), does increase the suspicion the issue is in gcc. Albeit not going to worry too much about it for qtwebengine. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=64afdb690871b92f6916abc03210662c43eb2d8f commit 64afdb690871b92f6916abc03210662c43eb2d8f Author: Ionen Wolkens <ionen@gentoo.org> AuthorDate: 2023-12-22 20:52:48 +0000 Commit: Ionen Wolkens <ionen@gentoo.org> CommitDate: 2023-12-24 08:27:32 +0000 dev-qt/qtwebengine: filter -march on arm64 with gcc for now (qt6) Bit like Qt5's webengine which did not respect it either. Not ideal but given the complexity tend to be lucky if it builds at all. As noted in the comment, please report if this works again so can cleanup (can test with USE=custom-cflags), may get fixed either by >=qtwebengine-6.7 (chromium-118) or a new gcc version depending on where the real issue is, but not planning to pursue this further myself. Closes: https://bugs.gentoo.org/920555 Closes: https://bugs.gentoo.org/920568 Signed-off-by: Ionen Wolkens <ionen@gentoo.org> dev-qt/qtwebengine/qtwebengine-6.6.1.ebuild | 6 ++++++ dev-qt/qtwebengine/qtwebengine-6.6.9999.ebuild | 6 ++++++ dev-qt/qtwebengine/qtwebengine-6.7.9999.ebuild | 6 ++++++ dev-qt/qtwebengine/qtwebengine-6.9999.ebuild | 6 ++++++ 4 files changed, 24 insertions(+) |