On 4/8/21 9:01 AM, Martin Jansa wrote:
* building chromium with gold and threads triggers this issue: [1/2] SOLINK ./libcbe.so FAILED: libcbe.so libcbe.so.TOC python "../../git/src/build/toolchain/gcc_solink_wrapper.py" --readelf="readelf" --nm="nm" --sofile="./libcbe.so" --tocfile="./libcbe.so.TOC" --output="./libcbe.so" -- i686-oe-linux-g++ -m32 -march=core2 -mtune=core2 -msse3 -mfpmath=sse -fstack-protector-strong -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=chromium/84.0.4147.89-4-r41.1/recipe-sysroot -shared -Wl,-soname="libcbe.so" -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,-z,defs -Wl,--as-needed -fuse-ld=gold -Wl,--threads -Wl,--thread-count=4 -m32 -Wl,-O2 -Wl,--gc-sections -rdynamic --sysroot=../../recipe-sysroot -L../../recipe-sysroot/lib -L../../recipe-sysroot/usr/lib -Lchromium/84.0.4147.89-4-r41.1/recipe-sysroot -o "./libcbe.so" @"./libcbe.so.rsp" collect2: fatal error: ld terminated with signal 11 [Segmentation fault] compilation terminated. * removing threads/thread-count is one possible work around, but then the use of gold for performance makes even less sense, that's why chromium from meta-browser uses LLD by default: https://github.com/OSSystems/meta-browser/commit/15228b01903d4ca801916e55c7618fa5a71019b7 https://lld.llvm.org/#performance but lets backport this as other recipes might also reproduce this issue
lgtm
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#150317): https://lists.openembedded.org/g/openembedded-core/message/150317 Mute This Topic: https://lists.openembedded.org/mt/81946021/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
