Re: [boost] Clang 4.0.0 MPL error in Boost next.hpp and prior.hpp

Subject: Re: [boost] Clang 4.0.0 MPL error in Boost next.hpp and prior.hpp
From: Edward Diener (eldiener_at_[hidden])
Date: 2017-03-27 16:24:40

On 3/27/2017 9:57 AM, Paul A. Bristow via Boost wrote:
>
>
>> -----Original Message-----
>> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Peter Dimov via Boost
>> Sent: 26 March 2017 17:11
>> To: boost_at_[hidden]
>> Cc: Peter Dimov
>> Subject: Re: [boost] Clang 4.0.0 MPL error in Boost next.hpp and prior.hpp
>>
>> Edward Diener wrote:
>>
>>> How did you get just clang.jam to work ? Doesn't it need VC++ support when
>>> using clang-cl ?
>>
>> I installed LLVM 4.0 in C:\LLVM and put
>>
>> using clang : 4.0 :
>>   "C:/LLVM/bin/clang.exe" :
>>   <compileflags>-fmsc-version=1910 <linkflags>-fuse-ld=lld ;
>>
>> in my user-config.jam. It found my VS 2017 installation by itself. There was
>> no need to use the developer command prompt or put anything into PATH.
>
> I'm trying to walk before I can run (but have stumbled :-( )
>
> I:\modular-boost\libs\hello_boost\example\jamfile.v2 just calls run hello_boost.cpp ;
>
> I have pulled Edward's pre-processor update
> https://github.com/boostorg/preprocessor/commit/dfc1c46ecedef21274eb142e267e91400aa33ec8
>
> and tried this in my user_config.jam
>
> with discouraging results.
>
> It picks up the compiler as expected (I think)
>
> notice: will use 'C:/LLVM/bin/clang.exe' for clang-linux, condition <toolset>clang-linux-4.0.0
>
> but doesn't find any targets or do anything beyond config checks???
>
> Performing configuration checks
>
>     - 32-bit                   : no  (cached)
>     - 64-bit                   : yes (cached)
>     - arm                      : no  (cached)
>     - mips1                    : no  (cached)
>     - power                    : no  (cached)
>     - sparc                    : no  (cached)
>     - x86                      : yes (cached)
>     - symlinks supported       : yes (cached)
>
> delete I:\modular-boost\bin.v2\libs\hello_boost to check what is created.  But there is no expected folders and files here.
>
> But I still only have VS 2015 14.0.25402.00 update 3RC - does this mean I need to update? (Sigh)
>
> Or use a different <compileflags>-fmsc-version=1910 ???

I use -fmsc-version=1900 for VS2015. My entry using the distributed 
clang 4.0 version, which by default targets VC++, is:

using clang : 4.0 : C:/Utilities/LLVM/400/x32/bin/clang++
  :
  <cxxflags>-fmacro-backtrace-limit=0
  <cxxflags>-Wno-invalid-token-paste
  <compileflags>-fmsc-version=1900
  <linkflags>-fuse-ld=lld
  ;

and is invoked with "toolset=clang-4.0".

>
> Or am I doing something silly?
>
> But thanks for making progress on this - I still hope to catch up.
>
> Paul
>
> PS I would use Cygwin, but I already have mingw installed and changing would muck other things up.