Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1074589 > unrolled thread
| Started by | Simon McVittie <smcv@debian.org> |
|---|---|
| First post | 2021-10-06 17:10 +0200 |
| Last post | 2021-10-12 04:30 +0200 |
| Articles | 8 — 4 participants |
Back to article view | Back to linux.debian.bugs.dist
Bug#995827: llvm-toolchain-13: FTBFS on armel, mipsel, mips64el: undefined references to __atomic_foo symbols Simon McVittie <smcv@debian.org> - 2021-10-06 17:10 +0200
Bug#995827: llvm-toolchain-13: FTBFS on armel, mipsel, mips64el: undefined references to __atomic_foo symbols Sylvestre Ledru <sylvestre@debian.org> - 2021-10-06 17:30 +0200
Bug#995827: llvm-toolchain-13: FTBFS on armel, mipsel, mips64el: undefined references to __atomic_foo symbols Nicholas D Steeves <sten@debian.org> - 2021-10-12 04:10 +0200
Bug#995827: llvm-toolchain-13: FTBFS on armel, mipsel, mips64el: undefined references to __atomic_foo symbols Sylvestre Ledru <sylvestre@debian.org> - 2021-10-21 08:30 +0200
Bug#995827: llvm-toolchain-13: FTBFS on armel, mipsel, mips64el: undefined references to __atomic_foo symbols Nicholas D Steeves <sten@debian.org> - 2021-10-26 19:40 +0200
Bug#995827: llvm-toolchain-13: FTBFS on armel, mipsel, mips64el: undefined references to __atomic_foo symbols Sylvestre Ledru <sylvestre@debian.org> - 2021-10-26 22:00 +0200
Bug#995827: llvm-toolchain-13: FTBFS on armel, mipsel, mips64el: undefined references to __atomic_foo symbols Nicholas D Steeves <sten@debian.org> - 2021-10-28 05:20 +0200
Bug#995827: llvm-toolchain-13: FTBFS on armel, mipsel, mips64el: undefined references to __atomic_foo symbols YunQiang Su <wzssyqa@gmail.com> - 2021-10-12 04:30 +0200
| From | Simon McVittie <smcv@debian.org> |
|---|---|
| Date | 2021-10-06 17:10 +0200 |
| Subject | Bug#995827: llvm-toolchain-13: FTBFS on armel, mipsel, mips64el: undefined references to __atomic_foo symbols |
| Message-ID | <D5gIp-1c8-9@gated-at.bofh.it> |
Source: llvm-toolchain-13
Version: 1:13.0.0-2
Severity: important
X-Debbugs-Cc: mesa@packages.debian.org, debian-mips@lists.debian.org, debian-arm@lists.debian.org
llvm-toolchain-13 has always failed to build on armel, mipsel, mips64el.
This makes mesa BD-Uninstallable on those release architectures since
its move to llvm-toolchain-13.
On armel:
> FAILED: bin/llvm-profdata
> : && /<<PKGBUILDDIR>>/build-llvm/./bin/clang++ -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough -Wcovered-switch-default -Wno-class-memaccess -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wmisleading-indentation -fdiagnostics-color -ffunction-sections -fdata-sections -O2 -DNDEBUG -g1 -marm -Wl,-z,relro -Wl,-rpath-link,/<<PKGBUILDDIR>>/build-llvm/tools/clang/stage2-bins/./lib -Wl,-O3 -Wl,--gc-sections tools/llvm-profdata/CMakeFiles/llvm-profdata.dir/llvm-profdata.cpp.o -o bin/llvm-profdata -Wl,-rpath,"\$ORIGIN/../lib" lib/libLLVM-13.so.1 -lpthread && :
> /usr/bin/arm-linux-gnueabi-ld: tools/llvm-profdata/CMakeFiles/llvm-profdata.dir/llvm-profdata.cpp.o: undefined reference to symbol '__atomic_fetch_add_4@@LIBATOMIC_1.0'
> /usr/bin/arm-linux-gnueabi-ld: /usr/lib/arm-linux-gnueabi/libatomic.so.1: error adding symbols: DSO missing from command line
On mips*el, the failure is in a different place, but might have the same
root cause (or not, clone this bug if necessary):
> FAILED: lib/clang/13.0.0/lib/linux/libclang_rt.scudo_standalone-mipsel.so
> : && /usr/bin/g++-10 -fPIC -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC -fno-semantic-interposition -fno-shrink-wrap -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wmisleading-indentation -fdiagnostics-color -ffunction-sections -fdata-sections -Wall -std=c++14 -Wno-unused-parameter -O2 -DNDEBUG -g1 -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -Wl,--build-id -Wl,-z,defs -Wl,-z,nodelete -mips32r2 -mabi=32 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wl,-z,defs,-z,now,-z,relro -ffunction-sections -fdata-sections -Wl,--gc-sections -pthread -Wl,-rpath-link,/<<PKGBUILDDIR>>/build-llvm/./lib -shared -Wl,-soname,libclang_rt.scudo_standalone-mipsel.so -o lib/clang/13.0.0/lib/linux/libclang_rt.scudo_standalone-mipsel.so projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/checksum.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/common.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/crc32_hw.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/flags_parser.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/flags.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/fuchsia.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/linux.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/release.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/report.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/string_utils.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_c.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_cpp.cpp.o -Wl,-rpath,"\$ORIGIN/../lib" && :
> /usr/bin/ld: projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_c.cpp.o: in function `scudo::atomic_u64::Type scudo::atomic_load<scudo::atomic_u64>(scudo::atomic_u64 const volatile*, scudo::memory_order)':
> /<<PKGBUILDDIR>>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: undefined reference to `__atomic_load_8'
> /usr/bin/ld: /<<PKGBUILDDIR>>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: undefined reference to `__atomic_load_8'
smcv
[toc] | [next] | [standalone]
| From | Sylvestre Ledru <sylvestre@debian.org> |
|---|---|
| Date | 2021-10-06 17:30 +0200 |
| Message-ID | <D5h1L-1iz-1@gated-at.bofh.it> |
| In reply to | #1074589 |
Le 06/10/2021 à 17:05, Simon McVittie a écrit : > Source: llvm-toolchain-13 > Version: 1:13.0.0-2 > Severity: important > X-Debbugs-Cc: mesa@packages.debian.org, debian-mips@lists.debian.org, debian-arm@lists.debian.org > > llvm-toolchain-13 has always failed to build on armel, mipsel, mips64el. > This makes mesa BD-Uninstallable on those release architectures since > its move to llvm-toolchain-13. > > On armel: >> FAILED: bin/llvm-profdata >> : && /<<PKGBUILDDIR>>/build-llvm/./bin/clang++ -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough -Wcovered-switch-default -Wno-class-memaccess -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wmisleading-indentation -fdiagnostics-color -ffunction-sections -fdata-sections -O2 -DNDEBUG -g1 -marm -Wl,-z,relro -Wl,-rpath-link,/<<PKGBUILDDIR>>/build-llvm/tools/clang/stage2-bins/./lib -Wl,-O3 -Wl,--gc-sections tools/llvm-profdata/CMakeFiles/llvm-profdata.dir/llvm-profdata.cpp.o -o bin/llvm-profdata -Wl,-rpath,"\$ORIGIN/../lib" lib/libLLVM-13.so.1 -lpthread && : >> /usr/bin/arm-linux-gnueabi-ld: tools/llvm-profdata/CMakeFiles/llvm-profdata.dir/llvm-profdata.cpp.o: undefined reference to symbol '__atomic_fetch_add_4@@LIBATOMIC_1.0' >> /usr/bin/arm-linux-gnueabi-ld: /usr/lib/arm-linux-gnueabi/libatomic.so.1: error adding symbols: DSO missing from command line > > On mips*el, the failure is in a different place, but might have the same > root cause (or not, clone this bug if necessary): >> FAILED: lib/clang/13.0.0/lib/linux/libclang_rt.scudo_standalone-mipsel.so >> : && /usr/bin/g++-10 -fPIC -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC -fno-semantic-interposition -fno-shrink-wrap -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wmisleading-indentation -fdiagnostics-color -ffunction-sections -fdata-sections -Wall -std=c++14 -Wno-unused-parameter -O2 -DNDEBUG -g1 -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -Wl,--build-id -Wl,-z,defs -Wl,-z,nodelete -mips32r2 -mabi=32 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wl,-z,defs,-z,now,-z,relro -ffunction-sections -fdata-sections -Wl,--gc-sections -pthread -Wl,-rpath-link,/<<PKGBUILDDIR>>/build-llvm/./lib -shared -Wl,-soname,libclang_rt.scudo_st andalone-mipsel.so -o lib/clang/13.0.0/lib/linux/libclang_rt.scudo_standalone-mipsel.so projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/checksum.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/common.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/crc32_hw.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/flags_parser.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/flags.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/fuchsia.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/linux.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/release.cpp.o projects/co mpiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/report.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/string_utils.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_c.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_cpp.cpp.o -Wl,-rpath,"\$ORIGIN/../lib" && : >> /usr/bin/ld: projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_c.cpp.o: in function `scudo::atomic_u64::Type scudo::atomic_load<scudo::atomic_u64>(scudo::atomic_u64 const volatile*, scudo::memory_order)': >> /<<PKGBUILDDIR>>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: undefined reference to `__atomic_load_8' >> /usr/bin/ld: /<<PKGBUILDDIR>>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: undefined reference to `__atomic_load_8' Yeah, I saw, it guess it is a -latomic missing again :) S
[toc] | [prev] | [next] | [standalone]
| From | Nicholas D Steeves <sten@debian.org> |
|---|---|
| Date | 2021-10-12 04:10 +0200 |
| Message-ID | <D7foR-1CE-1@gated-at.bofh.it> |
| In reply to | #1074594 |
[Multipart message — attachments visible in raw view] — view raw
Hi Sylvestre, Sylvestre Ledru <sylvestre@debian.org> writes: > Le 06/10/2021 à 17:05, Simon McVittie a écrit : >>> /usr/bin/ld: projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_c.cpp.o: in function `scudo::atomic_u64::Type scudo::atomic_load<scudo::atomic_u64>(scudo::atomic_u64 const volatile*, scudo::memory_order)': >>> /<<PKGBUILDDIR>>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: undefined reference to `__atomic_load_8' >>> /usr/bin/ld: /<<PKGBUILDDIR>>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: undefined reference to `__atomic_load_8' > Yeah, I saw, it guess it is a -latomic missing again :) > I've subscribed to this bug, since I just noticed llvm-toolchain-13 was available, and irony-mode users always want to use the latest Clang. Most irony-mode users are on amd64, so I'm thinking about switching now (for the greatest good), but I'm wondering this: Given that you know what the cause is, do you think this bug will soon be resolved? Thanks! Nicholas
[toc] | [prev] | [next] | [standalone]
| From | Sylvestre Ledru <sylvestre@debian.org> |
|---|---|
| Date | 2021-10-21 08:30 +0200 |
| Message-ID | <DazKq-6QM-5@gated-at.bofh.it> |
| In reply to | #1075303 |
Hello, Le 12/10/2021 à 03:51, Nicholas D Steeves a écrit : > Hi Sylvestre, > > Sylvestre Ledru <sylvestre@debian.org> writes: > >> Le 06/10/2021 à 17:05, Simon McVittie a écrit : >>>> /usr/bin/ld: projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_c.cpp.o: in function `scudo::atomic_u64::Type scudo::atomic_load<scudo::atomic_u64>(scudo::atomic_u64 const volatile*, scudo::memory_order)': >>>> /<<PKGBUILDDIR>>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: undefined reference to `__atomic_load_8' >>>> /usr/bin/ld: /<<PKGBUILDDIR>>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: undefined reference to `__atomic_load_8' >> Yeah, I saw, it guess it is a -latomic missing again :) >> > > I've subscribed to this bug, since I just noticed llvm-toolchain-13 was > available, and irony-mode users always want to use the latest Clang. > Most irony-mode users are on amd64, so I'm thinking about switching now > (for the greatest good), but I'm wondering this: Given that you know > what the cause is, do you think this bug will soon be resolved? > I think i fixed that one but not sure yet if there is other pending issue See: https://buildd.debian.org/status/package.php?p=llvm-toolchain-13 (it looks good for now) Cheers, Sylvestre
[toc] | [prev] | [next] | [standalone]
| From | Nicholas D Steeves <sten@debian.org> |
|---|---|
| Date | 2021-10-26 19:40 +0200 |
| Message-ID | <DcyAx-6Or-5@gated-at.bofh.it> |
| In reply to | #1077078 |
[Multipart message — attachments visible in raw view] — view raw
Sylvestre Ledru <sylvestre@debian.org> writes: > Hello, > > Le 12/10/2021 à 03:51, Nicholas D Steeves a écrit : [snip] >>> Le 06/10/2021 à 17:05, Simon McVittie a écrit : >>>>> /usr/bin/ld: projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_c.cpp.o: in function `scudo::atomic_u64::Type scudo::atomic_load<scudo::atomic_u64>(scudo::atomic_u64 const volatile*, scudo::memory_order)': >>>>> /<<PKGBUILDDIR>>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: undefined reference to `__atomic_load_8' >>>>> /usr/bin/ld: /<<PKGBUILDDIR>>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: undefined reference to `__atomic_load_8' >>> Yeah, I saw, it guess it is a -latomic missing again :) >>> >> >> I've subscribed to this bug, since I just noticed llvm-toolchain-13 was >> available, and irony-mode users always want to use the latest Clang. >> Most irony-mode users are on amd64, so I'm thinking about switching now >> (for the greatest good), but I'm wondering this: Given that you know >> what the cause is, do you think this bug will soon be resolved? >> > > > I think i fixed that one but not sure yet if there is other pending issue > See: > https://buildd.debian.org/status/package.php?p=llvm-toolchain-13 > (it looks good for now) > Thank you Sylvestre! Much appreciated :-) I think the following two RC bugs may be new since our last correspondence: #996632 and #996448 By the way, am I correct in understand that the focus for bookwork will be on llvm-toolchain-13 (or possibly 14)? Regards, Nicholas
[toc] | [prev] | [next] | [standalone]
| From | Sylvestre Ledru <sylvestre@debian.org> |
|---|---|
| Date | 2021-10-26 22:00 +0200 |
| Message-ID | <DcAM2-852-9@gated-at.bofh.it> |
| In reply to | #1078159 |
Le 26/10/2021 à 19:31, Nicholas D Steeves a écrit : > Sylvestre Ledru <sylvestre@debian.org> writes: > >> Hello, >> >> Le 12/10/2021 à 03:51, Nicholas D Steeves a écrit : > [snip] >>>> Le 06/10/2021 à 17:05, Simon McVittie a écrit : >>>>>> /usr/bin/ld: projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_c.cpp.o: in function `scudo::atomic_u64::Type scudo::atomic_load<scudo::atomic_u64>(scudo::atomic_u64 const volatile*, scudo::memory_order)': >>>>>> /<<PKGBUILDDIR>>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: undefined reference to `__atomic_load_8' >>>>>> /usr/bin/ld: /<<PKGBUILDDIR>>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: undefined reference to `__atomic_load_8' >>>> Yeah, I saw, it guess it is a -latomic missing again :) >>>> >>> I've subscribed to this bug, since I just noticed llvm-toolchain-13 was >>> available, and irony-mode users always want to use the latest Clang. >>> Most irony-mode users are on amd64, so I'm thinking about switching now >>> (for the greatest good), but I'm wondering this: Given that you know >>> what the cause is, do you think this bug will soon be resolved? >>> >> >> I think i fixed that one but not sure yet if there is other pending issue >> See: >> https://buildd.debian.org/status/package.php?p=llvm-toolchain-13 >> (it looks good for now) >> > Thank you Sylvestre! Much appreciated :-) I think the following two RC > bugs may be new since our last correspondence: #996632 and #996448 Yeah, I saw. I will probably just disable these tests for these archs. > > By the way, am I correct in understand that the focus for bookwork will > be on llvm-toolchain-13 (or possibly 14)? I guess you mean Bookworm. if this is the case, no, it will probably much more than that. Debian releases every 2 years, LLVM/Clang every 6 months. So, probably 16 or 17. Cheers Sylvestre
[toc] | [prev] | [next] | [standalone]
| From | Nicholas D Steeves <sten@debian.org> |
|---|---|
| Date | 2021-10-28 05:20 +0200 |
| Message-ID | <Dd47o-Kk-5@gated-at.bofh.it> |
| In reply to | #1078177 |
[Multipart message — attachments visible in raw view] — view raw
Sylvestre Ledru <sylvestre@debian.org> writes: > Le 26/10/2021 à 19:31, Nicholas D Steeves a écrit : >> By the way, am I correct in understand that the focus for bookwork will >> be on llvm-toolchain-13 (or possibly 14)? > > I guess you mean Bookworm. if this is the case, no, it will probably > much more than that. > Yes, thanks, that's what I meant. No pun intended :-$ (Aie! It looks like a textbook example of "freudian slip") > Debian releases every 2 years, LLVM/Clang every 6 months. So, probably > 16 or 17. > Ah, thanks, I hadn't realised that LLVM/Clang major releases were so frequent. Oh my goodness, that must be so hard to keep pace with! Thank you so much for your work to keep pace with such a moving target. Wow! I wish I could help out with the more challenging bugs... Regards, Nicholas
[toc] | [prev] | [next] | [standalone]
| From | YunQiang Su <wzssyqa@gmail.com> |
|---|---|
| Date | 2021-10-12 04:30 +0200 |
| Message-ID | <D7fId-1Pd-7@gated-at.bofh.it> |
| In reply to | #1074589 |
Simon McVittie <smcv@debian.org> 于2021年10月6日周三 下午11:09写道:
>
> Source: llvm-toolchain-13
> Version: 1:13.0.0-2
> Severity: important
> X-Debbugs-Cc: mesa@packages.debian.org, debian-mips@lists.debian.org, debian-arm@lists.debian.org
>
> llvm-toolchain-13 has always failed to build on armel, mipsel, mips64el.
> This makes mesa BD-Uninstallable on those release architectures since
> its move to llvm-toolchain-13.
>
> On armel:
> > FAILED: bin/llvm-profdata
> > : && /<<PKGBUILDDIR>>/build-llvm/./bin/clang++ -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough -Wcovered-switch-default -Wno-class-memaccess -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wmisleading-indentation -fdiagnostics-color -ffunction-sections -fdata-sections -O2 -DNDEBUG -g1 -marm -Wl,-z,relro -Wl,-rpath-link,/<<PKGBUILDDIR>>/build-llvm/tools/clang/stage2-bins/./lib -Wl,-O3 -Wl,--gc-sections tools/llvm-profdata/CMakeFiles/llvm-profdata.dir/llvm-profdata.cpp.o -o bin/llvm-profdata -Wl,-rpath,"\$ORIGIN/../lib" lib/libLLVM-13.so.1 -lpthread && :
> > /usr/bin/arm-linux-gnueabi-ld: tools/llvm-profdata/CMakeFiles/llvm-profdata.dir/llvm-profdata.cpp.o: undefined reference to symbol '__atomic_fetch_add_4@@LIBATOMIC_1.0'
> > /usr/bin/arm-linux-gnueabi-ld: /usr/lib/arm-linux-gnueabi/libatomic.so.1: error adding symbols: DSO missing from command line
>
> On mips*el, the failure is in a different place, but might have the same
> root cause (or not, clone this bug if necessary):
> > FAILED: lib/clang/13.0.0/lib/linux/libclang_rt.scudo_standalone-mipsel.so
> > : && /usr/bin/g++-10 -fPIC -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC -fno-semantic-interposition -fno-shrink-wrap -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wmisleading-indentation -fdiagnostics-color -ffunction-sections -fdata-sections -Wall -std=c++14 -Wno-unused-parameter -O2 -DNDEBUG -g1 -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -Wl,--build-id -Wl,-z,defs -Wl,-z,nodelete -mips32r2 -mabi=32 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wl,-z,defs,-z,now,-z,relro -ffunction-sections -fdata-sections -Wl,--gc-sections -pthread -Wl,-rpath-link,/<<PKGBUILDDIR>>/build-llvm/./lib -shared -Wl,-soname,libclang_rt.scudo_standalone-mipsel.so -o lib/clang/13.0.0/lib/linux/libclang_rt.scudo_standalone-mipsel.so projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/checksum.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/common.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/crc32_hw.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/flags_parser.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/flags.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/fuchsia.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/linux.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/release.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/report.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/string_utils.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_c.cpp.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_cpp.cpp.o -Wl,-rpath,"\$ORIGIN/../lib" && :
> > /usr/bin/ld: projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_c.cpp.o: in function `scudo::atomic_u64::Type scudo::atomic_load<scudo::atomic_u64>(scudo::atomic_u64 const volatile*, scudo::memory_order)':
> > /<<PKGBUILDDIR>>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: undefined reference to `__atomic_load_8'
> > /usr/bin/ld: /<<PKGBUILDDIR>>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: undefined reference to `__atomic_load_8'
>
With this patch, I can this error has been gone:
Index: llvm-toolchain-13-13.0.0/compiler-rt/lib/scudo/standalone/CMakeLists.txt
===================================================================
--- llvm-toolchain-13-13.0.0.orig/compiler-rt/lib/scudo/standalone/CMakeLists.txt
+++ llvm-toolchain-13-13.0.0/compiler-rt/lib/scudo/standalone/CMakeLists.txt
@@ -137,6 +137,13 @@ append_list_if(COMPILER_RT_HAS_LIBPTHREA
append_list_if(FUCHSIA zircon SCUDO_LINK_LIBS)
+if(CMAKE_HOST_SYSTEM_PROCESSOR MATCHES "mips" OR
+ CMAKE_HOST_SYSTEM_PROCESSOR MATCHES "mips64" OR
+ CMAKE_HOST_SYSTEM_PROCESSOR MATCHES "mipsel" OR
+ CMAKE_HOST_SYSTEM_PROCESSOR MATCHES "mips64el")
+ list(APPEND SCUDO_LINK_LIBS atomic)
+endif()
+
if(COMPILER_RT_HAS_SCUDO_STANDALONE)
add_compiler_rt_object_libraries(RTScudoStandalone
ARCHS ${SCUDO_STANDALONE_SUPPORTED_ARCH}
But I meet a new problem:
/build/llvm-toolchain-13-13.0.0/lldb/source/Plugins/Process/Linux/NativeThreadLinux.cpp:96:
undefined reference to
`lldb_private::process_linux::NativeRegisterContextLinux::CreateHostNativeRegisterContextLinux(lldb_private::ArchSpec
const&, lldb_private::process_linux::NativeThreadLinux&)'
/usr/bin/mips64el-linux-gnuabi64-ld:
/build/llvm-toolchain-13-13.0.0/lldb/source/Plugins/Process/Linux/NativeThreadLinux.cpp:96:
undefined reference to
`lldb_private::process_linux::NativeRegisterContextLinux::CreateHostNativeRegisterContextLinux(lldb_private::ArchSpec
const&, lldb_private::process_linux::NativeThreadLinux&)'
I am digging it.
> smcv
>
--
YunQiang Su
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web