Your message dated Tue, 22 Oct 2019 23:58:33 -0500
with message-id <3665822.Y3F6AO4q31@riemann>
and subject line Re: Bug#941780: castxml: FTBFS on armel: undefined reference
to symbol '__atomic_load_4@@LIBATOMIC_1.0'
has caused the Debian Bug report #941780,
regarding castxml: FTBFS on armel: undefined reference to symbol
'__atomic_load_4@@LIBATOMIC_1.0'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
941780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: castxml
Version: 0.1+git20180702-3
Severity: serious
Tags: ftbfs
Hi Maintainer
A recent rebuild of castxml failed to build from source on armel [1].
I've copied what I hope is the relevant part of the log below.
I believe this may be related to the recent switch from GCC 8 to 9.
"GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source."
Regards
Graham
[1]
https://buildd.debian.org/status/fetch.php?pkg=castxml&arch=armel&ver=0.1%2Bgit20180702-3%2Bb1&stamp=1569346877&raw=0
/usr/bin/c++ -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fno-exceptions -fno-rtti -std=c++11 -Wl,-z,relro
-Wl,-z,now -latomic -rdynamic CMakeFiles/castxml.dir/castxml.cxx.o
CMakeFiles/castxml.dir/Detect.cxx.o
CMakeFiles/castxml.dir/Output.cxx.o
CMakeFiles/castxml.dir/RunClang.cxx.o
CMakeFiles/castxml.dir/Utils.cxx.o -o ../bin/castxml
-L/usr/lib/llvm-8/lib -Wl,-rpath,/usr/lib/llvm-8/lib: -lclangFrontend
-lclangDriver -lclangSerialization -lclangParse -lclangSema
-lclangAnalysis -lclangEdit -lclangAST -lclangLex -lclangBasic
/usr/lib/llvm-8/lib/libLLVM-8.so.1
/usr/bin/ld:
/usr/lib/llvm-8/lib/libclangFrontend.a(SerializedDiagnosticReader.cpp.o):
undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libatomic.so: error
adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make[3]: *** [src/CMakeFiles/castxml.dir/build.make:148: bin/castxml] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-arm-linux-gnueabi'
make[2]: *** [CMakeFiles/Makefile2:1022: src/CMakeFiles/castxml.dir/all] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-arm-linux-gnueabi'
make[1]: *** [Makefile:144: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>/obj-arm-linux-gnueabi'
dh_auto_build: cd obj-arm-linux-gnueabi && make -j4 returned exit code 2
make: *** [debian/rules:15: build-arch] Error 255
--- End Message ---
--- Begin Message ---
On Saturday, October 5, 2019 5:20:53 A.M. CDT you wrote:
> Source: castxml
> Version: 0.1+git20180702-3
> Severity: serious
> Tags: ftbfs
>
> Hi Maintainer
>
> A recent rebuild of castxml failed to build from source on armel [1].
> I've copied what I hope is the relevant part of the log below.
Fixed in the 0.2.0-3 upload.
-Steve
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
