https://bugzilla.redhat.com/show_bug.cgi?id=1356907
--- Comment #3 from Josh Stone <[email protected]> --- Nearly 6 hours later, armv7hl failed a few run-pass tests like so: > error: linking with `cc` failed: exit code: 1 > note: "cc" "-Wl,--as-needed" "-Wl,-z,noexecstack" "-L" > "/builddir/build/BUILD/rustc-1.10.0/armv7-unknown-linux-gnueabihf/stage2/lib/rustlib/armv7-unknown-linux-gnueabihf/lib" > "armv7-unknown-linux-gnueabihf/test/run-pass/vec-macro-no-std.0.o" "-o" > "armv7-unknown-linux-gnueabihf/test/run-pass/vec-macro-no-std.stage2-armv7-unknown-linux-gnueabihf" > "-Wl,--gc-sections" "-pie" "-Wl,-O1" "-nodefaultlibs" "-L" > "armv7-unknown-linux-gnueabihf/test/run-pass/" "-L" > "armv7-unknown-linux-gnueabihf/test/run-pass/vec-macro-no-std.stage2-armv7-unknown-linux-gnueabihf.run-pass.libaux" > "-L" "armv7-unknown-linux-gnueabihf/rt" "-L" > "/builddir/build/BUILD/rustc-1.10.0/armv7-unknown-linux-gnueabihf/stage2/lib/rustlib/armv7-unknown-linux-gnueabihf/lib" > "-Wl,-Bstatic" "-Wl,-Bdynamic" "-L" > "/builddir/build/BUILD/rustc-1.10.0/armv7-unknown-linux-gnueabihf/stage2/lib/rustlib/armv7-unknown-linux-gnueabihf/lib" > "-l" "std-e8edd0fd" "-l" "dl" "-l" "pthread" "-l" "gcc_s" "-l" "c" "-l" "m" > "-l" "rt" "-l" "util" "-l" "compiler-rt" > note: /usr/bin/ld: /usr/lib/libc_nonshared.a(elf-init.oS): undefined > reference to symbol '__aeabi_unwind_cpp_pr0@@GCC_3.5' > /lib/libgcc_s.so.1: error adding symbols: DSO missing from command line > collect2: error: ld returned 1 exit status > error: aborting due to previous error I think there's a c/gcc_s interdependency that's not correctly managed here. At least on x86_64, the default C link line has something like this: > -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s > --no-as-needed i.e. -lgcc_s is positioned twice as-needed, before and after -lc. I will see if I can reproduce this locally and file an rust issue. For now, I think we should leave rust.spec as i686/x86_64 only, citing Tier 1 status. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list [email protected] https://lists.fedoraproject.org/admin/lists/[email protected]
