/usr/lib/gcc/x86_64-pc-linux-gnu/10.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: LoadableModule.o: warning: relocation against `lt__PROGRAM__LTX_preloaded_symbols' in read-only section `.text' /usr/lib/gcc/x86_64-pc-linux-gnu/10.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: LoadableModule.o: in function `LoadableModule::LoadableModule(String const&)': LoadableModule.cc:(.text+0x47): undefined reference to `lt__PROGRAM__LTX_preloaded_symbols' /usr/lib/gcc/x86_64-pc-linux-gnu/10.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: warning: creating DT_TEXTREL in a PIE collect2: error: ld returned 1 exit status rdlibtool: exec error upon slbt_exec_link_create_executable(), line 1731: (see child process error messages). ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no-multilib_hardened-20210401-181817 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.3.1 [3] x86_64-pc-linux-gnu-10.3.0 * clang version 11.1.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.1.0 Python 3.8.9 Available Ruby profiles: (none found) Available Rust versions: [1] rust-bin-1.51.0 [2] rust-1.51.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.282_p08 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Sat Apr 10 17:35:14 UTC 2021 emerge -qpvO net-proxy/squid [ebuild N ] net-proxy/squid-4.14 USE="htcp ipv6 pam ssl wccp wccpv2 -caps -ecap -esi -gnutls (-ipf-transparent) -kerberos (-kqueue) -ldap -logrotate -mysql -nis -perl (-pf-transparent) -postgres -qos -radius -samba -sasl (-selinux) -snmp -sqlite -ssl-crtd -systemd -test -tproxy"
Created attachment 699063 [details] emerge-info.txt
Created attachment 699066 [details] emerge-history.txt
Created attachment 699069 [details] environment
Created attachment 699072 [details] etc.portage.tar.bz2
Created attachment 699075 [details] logs.tar.bz2
Created attachment 699078 [details] net-proxy:squid-4.14:20210410-180609.log.bz2
Created attachment 699081 [details] temp.tar.bz2
AFAIK this is long dead, Squid 6.x in tree builds with current GCC in tree.
I can still reproduce this with net-proxy/squid-6.6::gentoo and they are still clearly using ltdl in src/LoadableModule.cc. This has nothing to do with gcc.
(In reply to orbea from comment #9) > I can still reproduce this with net-proxy/squid-6.6::gentoo and they are > still clearly using ltdl in src/LoadableModule.cc. This has nothing to do > with gcc. Oh, after a while puzzling over what was different, I finally noticed the fine print, that this failure is when using rdlibtool from slibtool. Nothing in the title or text said that, I chased dead ends before finally noticing the rdlibtool: lines in the logs and the block on an slibtool bug and Googled to figure out what all that is about. So anyway, yes now I can reproduce this as well. I've filed an upstream bug: https://bugs.squid-cache.org/show_bug.cgi?id=5339 I'd be glad to take a patch but I'm unlikely to spend enough cycles figuring out how to do a fix on my own. Would it be possible for build bot bugs filed when using nonstandard toolchains to be marked more obviously as such/highlighting what's being tested? Or is that supposed to be evident from the Blocks: reference and I just missed it?
If you see the "Blocks" field it clearly says "slibtool", but this is a long standing issue with slibtool and not necessarily Squid. Although arguable it would still be good for them to not use ltdl.
Fixed in slibtool-9999.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=341f85a7caa16a7d986a4b428521562bf9120b08 commit 341f85a7caa16a7d986a4b428521562bf9120b08 Author: orbea <orbea@riseup.net> AuthorDate: 2024-03-15 13:51:37 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-03-15 19:29:22 +0000 dev-build/slibtool: add 0.5.36 Many bugs are fixed with this release, it is recommended for slibtool users to rebuild their entire system after this release. The addition of -export-symbols and -export-symbols-regex will allow exporting only the desired public symbols globally in any package that uses them. Closes: https://bugs.gentoo.org/925555 Closes: https://bugs.gentoo.org/913670 Closes: https://bugs.gentoo.org/916128 Closes: https://bugs.gentoo.org/775596 Closes: https://bugs.gentoo.org/792072 Closes: https://bugs.gentoo.org/924407 Closes: https://bugs.gentoo.org/924291 Closes: https://bugs.gentoo.org/782013 Closes: https://bugs.gentoo.org/914569 Closes: https://bugs.gentoo.org/791880 Closes: https://bugs.gentoo.org/913551 Closes: https://bugs.gentoo.org/913688 Closes: https://bugs.gentoo.org/914097 Closes: https://bugs.gentoo.org/915966 Closes: https://bugs.gentoo.org/924408 Closes: https://bugs.gentoo.org/915121 Closes: https://bugs.gentoo.org/913642 Closes: https://bugs.gentoo.org/917639 Closes: https://bugs.gentoo.org/917640 Closes: https://bugs.gentoo.org/913530 Closes: https://bugs.gentoo.org/913638 Closes: https://bugs.gentoo.org/778515 Closes: https://bugs.gentoo.org/920190 Closes: https://bugs.gentoo.org/924404 Signed-off-by: orbea <orbea@riseup.net> Signed-off-by: Sam James <sam@gentoo.org> dev-build/slibtool/Manifest | 2 ++ dev-build/slibtool/slibtool-0.5.36.ebuild | 41 +++++++++++++++++++++++++++++++ 2 files changed, 43 insertions(+)
