"recent libcxx regression" reason discovered. clang version info/folder changed. possibly accidental?

Tom Stellard thomas.stellard at amd.com
Wed Mar 5 09:17:22 PST 2014


On 03/05/2014 03:03 AM, Reid Kleckner wrote:
> This was probably caused by r202720.  I guess that's desirable if we
> want to update our builtin headers in a patch release, but it'd be nice
> if we did what gcc does and symlink 3.5 to 3.5.0 or something.
>

Thanks for raising this issue.  I think we should be able to add
a symlink from major.minor to major.minor.patch.  I will work on a patch
for this.

-Tom

>
> On Tue, Mar 4, 2014 at 3:59 AM, G M <gmisocpp at gmail.com
> <mailto:gmisocpp at gmail.com>> wrote:
>
>     Hi Everyone
>
>     It would appear that the recent build problems that suddenly
>     appeared for me that were manifesting through libcxx no longer
>     building was caused by the clang headers changing directory or
>     something like that.
>
>     Files like x86intrin.h were in
>
>     \llvm\lib\clang\3.5\include
>
>     but somehow for some reason changed to
>
>     \llvm\lib\clang\3.5.0\include
>
>     This may be intentional but I thought I'd call my discovery out
>     since it might be accidental and may cause other people problems
>     like it did me.
>
>     In my case It resulted in a simple hard coded script I had failing
>     to pickup the latest versions of headers because they "moved"
>     unexpectedly.
>
>     I changed my local custom script to note that ,0 change and
>     everything builds again now.
>
>     Hope this info is useful to others.
>
>     _______________________________________________
>     cfe-commits mailing list
>     cfe-commits at cs.uiuc.edu <mailto:cfe-commits at cs.uiuc.edu>
>     http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
>
>





More information about the cfe-commits mailing list