[LLVMbugs] [Bug 11298] unable to find crtbegin.o, lgcc, lgcc_s on my host/platform Gentoo

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Wed Nov 2 13:11:59 PDT 2011


Chandler Carruth <chandlerc at gmail.com> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #9 from Chandler Carruth <chandlerc at gmail.com> 2011-11-02 15:11:59 CDT ---
(In reply to comment #8)
> > If this is the case, using it turns off most of the clever GCC installation
> > auto-detection. Is there a reason you're using that? It's all a bit of a hack,
> > and really poorly tested. If without it you have problems finding libraries or
> > headers, we can just fix the underlying code.
> I'm not intentionally defining it.  I'm emerging the default 9999 ebuild. 
> Would this be the offending param?
>  --with-cxx-include-root=/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/include/g++-v4

That sounds quite likely. You should file a bug with Gentoo (or wherever you
got the 9999 ebuild) and have them stop doing that.

Instead, when a new GCC version comes out that Clang doesn't support, they
should file bugs / patch the Clang source code to support them; specifically
InitHeaderSearch.cpp. We've fixed Clang to automatically detect and use newer
GCC installations when linking, but not the libstdc++ headers.

I'd love to see us eventually have an easy way to at configure time hard code
all the relevant paths, but more than that I'd like the Clang binary by default
to Just Work on most distros and even as GCC gets upgraded. Thus, I've focused
most of my efforts there. I've added support to Clang for finding and using GCC
4.5.3 headers on Gentoo in r143567. Let me know if you need any additional
paths added.

Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

More information about the llvm-bugs mailing list