similar to: [LLVMdev] Building llvm from source with clang instead of gcc

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

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 to the clang/clang++ binaries before running configure. -Krzysztof --

On 1/5/2013 11:48 AM, Edward Diener wrote: > > It would have been much better if the environment variables were named > LLVM_CC and LLVM_CXX for the obvious reason that CC and CXX are very > common names. Actually, the variables CC and CXX are used exactly as they are always used: to set the C and C++ compiler. Frankly, I don't see why you would prefer to use different ones.

On 1/5/2013 8:01 PM, Justin Holewinski wrote: > > On Sat, Jan 5, 2013 at 5:59 PM, Edward Diener > <eldlistmailingz at tropicsoft.com <mailto:eldlistmailingz at tropicsoft.com>> > wrote: > > On 01/05/2013 01:11 PM, Dmitri Gribenko wrote: > > On Sat, Jan 5, 2013 at 7:48 PM, Edward Diener > <eldlistmailingz at tropicsoft.__com >

On 01/05/2013 01:11 PM, Dmitri Gribenko wrote: > On Sat, Jan 5, 2013 at 7:48 PM, Edward Diener > <eldlistmailingz at tropicsoft.com> wrote: >> I actually 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

On Sat, Jan 5, 2013 at 5:59 PM, Edward Diener < eldlistmailingz at tropicsoft.com> wrote: > On 01/05/2013 01:11 PM, Dmitri Gribenko wrote: > >> On Sat, Jan 5, 2013 at 7:48 PM, Edward Diener >> <eldlistmailingz at tropicsoft.**com <eldlistmailingz at tropicsoft.com>> >> wrote: >> >>> I actually found out that llvm/configure will choose

On Sat, Jan 5, 2013 at 11:08 PM, Edward Diener < eldlistmailingz at tropicsoft.com> wrote: > On 1/5/2013 8:01 PM, Justin Holewinski wrote: > >> >> On Sat, Jan 5, 2013 at 5:59 PM, Edward Diener >> <eldlistmailingz at tropicsoft.**com <eldlistmailingz at tropicsoft.com><mailto: >> eldlistmailingz@**tropicsoft.com <eldlistmailingz at

On 1/6/2013 9:47 AM, Justin Holewinski wrote: > On Sat, Jan 5, 2013 at 11:08 PM, Edward Diener > <eldlistmailingz at tropicsoft.com <mailto:eldlistmailingz at tropicsoft.com>> > wrote: > > On 1/5/2013 8:01 PM, Justin Holewinski wrote: > > > On Sat, Jan 5, 2013 at 5:59 PM, Edward Diener > <eldlistmailingz at tropicsoft.__com >

On Sat, Jan 5, 2013 at 7:48 PM, Edward Diener <eldlistmailingz at tropicsoft.com> wrote: > I actually 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.

Edward Diener <eldlistmailingz at tropicsoft.com> writes: >> Clang will attempt to use your installed system libraries, usually >> libstdc++ and glibc on a Linux distribution. We could probably maintain >> a libstdc++ compatibility table that says clang x.y is compatible with >> libstdc++ up to z.w. In the vast majority of cases, this just works if >> you

On 1/15/2013 11:19 AM, Dmitri Gribenko wrote: > On Mon, Jan 14, 2013 at 3:32 AM, Edward Diener > <eldlistmailingz at tropicsoft.com> wrote: >> It is on pastebin and is called ConfigureLog. I made it private, FWIW. > > Please provide a link. I can not find it because it is private. I copied it to a public paste called ConfigureLogPublic at http://pastebin.com/yaLHmmGk.

On 01/09/2013 10:37 AM, Dmitri Gribenko wrote: > On Tue, Jan 8, 2013 at 8:43 AM, Edward Diener > <eldlistmailingz at tropicsoft.com> wrote: >> After applying your patch on Mageia 2 and invoking llvm's configure: >> >> Using clang 3.0 I get: >> >> "checking whether clang works... no >> configure: error: Selected compiler could not find or

On 01/07/2013 08:39 AM, Dmitri Gribenko wrote: > On Mon, Jan 7, 2013 at 12:23 AM, Edward Diener > <eldlistmailingz at tropicsoft.com> wrote: >> On Mageia 2 I have installed the binary clang package clang3.0-7. When I >> tried to build the latest llvm/clang from source using this binary clang >> I get this error: >> >> 1) In file included from >>

On Wednesday, January 16, 2013, Edward Diener wrote: > On 1/15/2013 11:19 AM, Dmitri Gribenko wrote: > >> On Mon, Jan 14, 2013 at 3:32 AM, Edward Diener >> <eldlistmailingz at tropicsoft.com> wrote: >> >>> It is on pastebin and is called ConfigureLog. I made it private, FWIW. >>> >> >> Please provide a link. I can not find it because it

On Tue, Jan 8, 2013 at 8:43 AM, Edward Diener <eldlistmailingz at tropicsoft.com> wrote: > After applying your patch on Mageia 2 and invoking llvm's configure: > > Using clang 3.0 I get: > > "checking whether clang works... no > configure: error: Selected compiler could not find or parse C++ standard > library headers. Rerun with CC=c-compiler CXX=c++-compiler

On Sun, Jan 13, 2013 at 12:59 AM, Edward Diener <eldlistmailingz at tropicsoft.com> wrote: > On 01/09/2013 10:37 AM, Dmitri Gribenko wrote: >> >> On Tue, Jan 8, 2013 at 8:43 AM, Edward Diener >> <eldlistmailingz at tropicsoft.com> wrote: >>> >>> After applying your patch on Mageia 2 and invoking llvm's configure: >>> >>>

On Mageia 2 I have installed the binary clang package clang3.0-7. When I tried to build the latest llvm/clang from source using this binary clang I get this error: 1) In file included from /home/mgeldiener/vcs/llvm/lib/Support/Signals.cpp:30: /home/mgeldiener/vcs/llvm/lib/Support/Unix/Signals.inc:32:10: fatal error: 'cxxabi.h' file not found #include <cxxabi.h> ^ llvm[1]:

On Mon, Jan 7, 2013 at 12:23 AM, Edward Diener <eldlistmailingz at tropicsoft.com> wrote: > On Mageia 2 I have installed the binary clang package clang3.0-7. When I > tried to build the latest llvm/clang from source using this binary clang > I get this error: > > 1) In file included from > /home/mgeldiener/vcs/llvm/lib/Support/Signals.cpp:30: >

On 01/12/2013 06:08 PM, Dmitri Gribenko wrote: > On Sun, Jan 13, 2013 at 12:59 AM, Edward Diener > <eldlistmailingz at tropicsoft.com> wrote: >> On 01/09/2013 10:37 AM, Dmitri Gribenko wrote: >>> >>> On Tue, Jan 8, 2013 at 8:43 AM, Edward Diener >>> <eldlistmailingz at tropicsoft.com> wrote: >>>> >>>> After applying your

How can I tell at compile time through predefined macros whether libc++ includes/supports the C++14 header file shared_mutex ? Given that I have identified that libc++ is being used, will this work ? : #if __cplusplus >= 201402 // Header file shared_mutex supported #endif or do I need to check something else ?