Description of problem: Clang's ASAN feature is broken in F18. ✗ cat main.c int main() {} ✗ clang -fsanitize=address main.c /usr/bin/ld: cannot find /usr/bin/../lib/clang/3.2/lib/linux/libclang_rt.asan-x86_64.a: No such file or directory clang: error: linker command failed with exit code 1 (use -v to see invocation) Version-Release number of selected component (if applicable): ✗ clang -v clang version 3.2 (tags/RELEASE_32/final) Target: x86_64-redhat-linux-gnu Thread model: posix Additional info: To fix this problem, build and ship "compiler-rt" component along with existing LLVM / Clang package(s). Other distributions have already fixed this problem. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674155 https://bugs.archlinux.org/task/29983
*** Bug 957587 has been marked as a duplicate of this bug. ***
Hi, Is there any progress on this bug? Are we going to ship a "broken" compiler again? :-(
Update: Clang's ASAN feature is still broken in Fedora 19.
Created attachment 768253 [details] updated SPEC file
Hi Adam, I have attached an updated SPEC file to fix the problem. It now builds LLVM 3.3 release (instead of building pre-releases) and ASAN feature now works great. Please test and let me know how it goes.
Seems that ASAN still missing in fedora 20 ... YC
Created attachment 807045 [details] newly updated SPEC file
Attached SPEC file seems to work. See http://koji.fedoraproject.org/koji/taskinfo?taskID=6019218
I would really love to see this working. Any update on this bug? (And other LLVM bugs? Just a few features provided by LLVM work in Fedora unfortunately.)
When you compile clang from sources, everything is working fine (tested with the git repo). It's a little bit long to compile, but all the plugins works.
I have submitted fixed (and tested!) .spec files multiple times already. I simply do not understand why it is taking so long (close to a year now!) to fix this trivial bug. Please allow someone else to maintain / co-maintain this package. I really don't want to use the "unresponsive maintainer" resolution path.
I wrote to Adam a few days ago and we talked about it. I'm looking into this and several other LLVM bugs. I will try to help Adam to resolve this bug ASAP.
*** Bug 1026101 has been marked as a duplicate of this bug. ***
llvm-3.3-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/llvm-3.3-2.fc20
Package llvm-3.3-2.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing llvm-3.3-2.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-22023/llvm-3.3-2.fc20 then log in and leave karma (feedback).
Confirming that it is working with the update. Will there be an update for Fedora 19 as well?
(In reply to David Highley from comment #16) > Confirming that it is working with the update. Will there be an update for > Fedora 19 as well? I'm not sure if update in F19 is safe enough. There were quite a lot of changes in the package. I want to be sure that I didn't break anything.
llvm-3.3-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/llvm-3.3-2.fc19
llvm-3.3-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/llvm-3.3-3.fc19
llvm-3.3-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
llvm-3.3-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.