search for: r171630

...gure will choose clang if it is >> found in the path. This contradicts what is written at >> http://llvm.org/docs/GettingStarted.html#requirements, where it says it >> will use the first GCC it finds. Perhaps that explanation needs to be >> updated. > > Updated docs in r171630. > >> Finally I found that if llvm/configure uses clang instead of gcc, it >> invariably fails on my Linux distros because it is using the gcc >> distributed included directories and an earlier version of clang will >> often fail with these gcc header files. Once I force...

...found out that llvm/configure will choose clang if it is > found in the path. This contradicts what is written at > http://llvm.org/docs/GettingStarted.html#requirements, where it says it > will use the first GCC it finds. Perhaps that explanation needs to be > updated. Updated docs in r171630. > Finally I found that if llvm/configure uses clang instead of gcc, it > invariably fails on my Linux distros because it is using the gcc > distributed included directories and an earlier version of clang will > often fail with these gcc header files. Once I force llvm/configure to &g...

...tp://llvm.org/docs/**GettingStarted.html#**requirements<http://llvm.org/docs/GettingStarted.html#requirements>, >>> where it says it >>> will use the first GCC it finds. Perhaps that explanation needs to be >>> updated. >>> >> >> Updated docs in r171630. >> >> Finally I found that if llvm/configure uses clang instead of gcc, it >>> invariably fails on my Linux distros because it is using the gcc >>> distributed included directories and an earlier version of clang will >>> often fail with these gcc header fil...

On 01/05/2013 11:32 AM, Krzysztof Parzyszek wrote: > On 1/5/2013 7:10 AM, Edward Diener wrote: >> Is it possible to build llvm with a previous version of clang installed >> as a binary ? If so, how do I get llvm/configure to use the binary >> version of clang rather than gcc to build the latest version of llvm ? >> > > Set environment variables CC and CXX to point

...l#__requirements > <http://llvm.org/docs/GettingStarted.html#requirements>, > where it says it > will use the first GCC it finds. Perhaps that explanation > needs to be > updated. > > > Updated docs in r171630. > > Finally I found that if llvm/configure uses clang instead of > gcc, it > invariably fails on my Linux distros because it is using the gcc > distributed included directories and an earlier version of > clang will >...

...rg/docs/GettingStarted.html#requirements> >> >, >> >> where it says it >> will use the first GCC it finds. Perhaps that explanation >> needs to be >> updated. >> >> >> Updated docs in r171630. >> >> Finally I found that if llvm/configure uses clang instead of >> gcc, it >> invariably fails on my Linux distros because it is using the >> gcc >> distributed included directories and an earlier version of &gt...

...tarted.html#requirements>>, > > where it says it > will use the first GCC it finds. Perhaps that > explanation > needs to be > updated. > > > Updated docs in r171630. > > Finally I found that if llvm/configure uses clang > instead of > gcc, it > invariably fails on my Linux distros because it is > using the gcc > distributed included director...