-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need help: libpsl build failure #1789
Comments
Could you please rebuild the libpsl image:
and answer y to
And try again? It's possible that a compiler change (in a base image) caused this. |
That's what I meant with "downloading the latest image". Sorry for being unprecise. |
Just tried it again, same results (only success, issue is not reproducible).
|
This specific failure in the icu configure affects libpsl, dlplibs and libreoffice. I tweaked the libreoffice build to dump the config.log on failure, because this is not happening locally and the error is... clang++ -stdlib=libc++ -fsanitize-blacklist=/src/libreoffice/bin/sanitize-blacklist.txt -o conftest -O1 -fno-omit-frame-pointer -gline-tables-only -DFUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION -fsanitize-coverage=bb,no-prune,trace-pc-guard -O0 -stdlib=libc++ -std=gnu++14 -O2 -fno-strict-aliasing -DU_USE_STRTOD_L=0 -W -Wall -pedantic -Wpointer-arith -Wwrite-strings -Wno-long-long -DHAVE_GCC_ATOMICS=0 -ffunction-sections -fdata-sections -Wl,--hash-style=gnu -Wl,-Bsymbolic-functions -Wl,--gc-sections conftest.cpp -lpthread -lm >&5 |
passing ac_cv_namespace_ok=yes to the icu configure should skip the test and default it to true. I'll try that for LibreOffice and see if it fails somewhere else. @dtardon FYI wrt the dlplibs build failure |
blast, still fails later... Step #20: /usr/bin/ld: icuinfo: sh_link of section |
@eugenis @kcc @morehouse any idea what might be causing this?
No idea why it doesn't reproduce locally... Only major difference should be the host kernel. |
I was able to reproduce the LibreOffice failure after updating the build image with When built as a static library without --disable-release icu is adding -ffunction-sections -fdata-sections to CXXFLAGS and -Wl,--gc-sections to LDFLAGS, --disable-release suppresses that so might also help in this libpsl/dlplibs case |
@morehouse Most certainly related to https://reviews.llvm.org/D50483. |
That does seem to be the problematic change. I can reproduce locally with BFD linker. One workaround is to use LLD or Gold linkers. Still looking for a better fix than just reverting the change, since it was done to fix a different problem... |
https://reviews.llvm.org/rL342186 fixes #1789 (comment) for me locally. @oliverchang Rolling past r342186 will probably fix this. |
Are we in rush on this or can wait a few days while Chromium rolls clang forward for us? |
green build |
The libicu dependency fails to build (all of a sudden), the ./configure run says
It looks like this is the ASAN build, so I tried to reproduce locally (infra/helper.py build_fuzzers --sanitizer libpsl) with the latest commit from upstream, and downloading the latest image.
Not to reproduce here :-(
Could someone take a look, please ?. The libicu version is the same since a long time (59.1), so I assume something changed in the environment.
See the current libpsl log at:
https://oss-fuzz-build-logs.storage.googleapis.com/log-496fcc8a-6de3-4198-97e8-410eda12e759.txt
The text was updated successfully, but these errors were encountered: