On Mon, Apr 25, 2011 at 12:08 PM, Jakub Wieczorek <[email protected]> wrote: > Hello, > > With GCC 4.6.0 installed in Arch Linux, clang doesn't search the > architecture specific subdirectory of the libstd++'s headers. > Attaching a patch that fixes the problem.
Landed in r130152. > While we're at it, is there a reason why the proper search paths are > not detected at run time similarly to how library paths are? Instead > of hard coding the GCC version for a particular distribution version, > it could simply look for all the versions and pick the newest one. In > the case of Arch, it is an even better idea because there are no Arch > releases per se and the user should be free to have whatever version > of GCC they want, no matter what the particular distro version is. On > top of that, it seems to me that mixing libraries from one GCC version > and headers from a different one might not always be safe, am I right? > I guess, in that case it doesn't really make a difference because the > dynamically detected library would always be at most newer than the > headers anyway. > > Would such a change be accepted? I'll be happy to do this. I don't know, but if it doesn't regress compile time (which it would if the change would start gcc processes or whatnot) I guess it would be accepted. I think there was a thread about this on this list yesterday or the day before. Nico > > Best regards, > Jakub Wieczorek > > _______________________________________________ > cfe-commits mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits > > _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
