[cfe-dev] Changing the way Clang's driver computes the library search paths on Linux

Chandler Carruth chandlerc at google.com
Sun Oct 2 19:31:44 PDT 2011

FYI, I've got VMs set up for most of the relevant distros at this point, and
I think the patch with one slight fix should be good to go. I'm planning on
committing it, along with improved sysroot support shortly. Once that's in,
I'll be testing it out on lots of different distros and fixing any fallout.

I'll try to get to Debian and get the substance of the patch posted rolled
in as well.


On Sun, Oct 2, 2011 at 1:54 AM, Chandler Carruth <chandlerc at google.com>wrote:

> Hello folks,
> I'd like to change the way that Clang's driver computes the library search
> paths on Linux. The current system is very ad-hoc, and does not match the
> reality of what GCC does. As Clang's driver strives for GCC compatibility,
> I'd like to address this by modeling the GCC behavior is closely as
> possible. I have attached a patch which does exactly this. To the best of my
> ability to test a trunk-built GCC through manipulating a fake filesystem's
> directory structure, this patch will make Clang search the same set of
> directories as GCC would. It also simplifies the logic significantly, and
> makes it less brittle in its assumptions about the underlying filesystem
> layout.
> Unless I hear objections, I plan to commit this as it in every way I can
> test it makes Clang's driver strictly more compatible with GCC, and makes it
> possible to fix several bugs when using Clang as part of a multilib
> cross-compiling toolchain. If there are specific distros which need special
> behavior, we should add that predicated on the distribution.
> Rafael, I CC-ed you because I know you've worked hard on this before, and
> may have a large number of distributions installed on VMs. If you can test
> Clang with this patch (or after I commit it) and report places where the
> behavior doesn't match GCC's that would be very helpful.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20111002/ff71ab1f/attachment.html>

More information about the cfe-dev mailing list