Created attachment 530935 [details] patch Description of problem: Any compilation with clang fails in the linker phase because of missing -L/usr/lib/gcc/x86_64-redhat-linux/4.6.2 . Version-Release number of selected component (if applicable): llvm-2.9-5.fc16.x86_64 How reproducible: always Steps to Reproduce: 1. echo 'int main(void) {return 0;}' > testcase.c 2. clang testcase.c Actual results: /usr/bin/ld: cannot find crtbegin.o: No such file or directory /usr/bin/ld: cannot find -lgcc /usr/bin/ld: cannot find -lgcc_s clang: error: linker command failed with exit code 1 (use -v to see invocation) Expected results: Compilation finishes and a.out is created.
*** Bug 755356 has been marked as a duplicate of this bug. ***
*** Bug 757241 has been marked as a duplicate of this bug. ***
Note: given that llvm needs exact version of gcc, it should use versioned require for it. This way this kind of problem would be detected by broken dependencies.
I've just been hit by this bug. Failed to link anything compiled with clang. Would it be worthwhile submitting an update with just this fix?
By all means, yes. It's not that it is useful for anything right now.
I thought I'd try out clang. So I installed it with yum, like I install all the other packages I want to try out. I don't think it's unreasonable that when I install a compiler package, I get a compiler that works. :-P I'm slightly surprised and disappointed that a bug that makes a package *completely useless* has been sitting around untouched for a month and a half!
*** Bug 770487 has been marked as a duplicate of this bug. ***
*** Bug 742406 has been marked as a duplicate of this bug. ***
The fix is dead simple: Add "4.6.2" to the list of gcc versions in clang-2.9-add_gcc_vers.patch (part of the SRPM) and rebuild. You might want to increment the release number in the .spec file so that the RPMs will be an upgrade.
I meant to add that since the patch is so simple, why can't this just be pushed out?
Apologies; was trying to fix another unrelated problem, but of course as you pointed out the supported compiler list needs updating. Thankfully this goes away with 3.0 (unfortunately we have bigger problems there with GCC 4.7)
llvm-2.9-6.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/llvm-2.9-6.fc16
Package llvm-2.9-6.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing llvm-2.9-6.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-1188/llvm-2.9-6.fc16 then log in and leave karma (feedback).
llvm-2.9-6.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.