Message: 1
Date: Sat, 2 Jul 2011 15:39:41 -0700 (PDT) From: Vicente Botet <vicente.botet@wanadoo.fr> To: boost-users@lists.boost.org Subject: Re: [Boost-users] [chrono] Can not build with intel-win Message-ID: <1309646381376-3641235.post@n4.nabble.com> Content-Type: text/plain; charset=UTF-8
Edward Rankin wrote:
Message du 13/06/11 09:12 De : "Bo Jensen" A : boost-users <at> lists.boost.org Copie ? : Objet : [Boost-users] [chrono] Can not build with intel-win
Newest intel C++ release and vs2010, can not build with chrono from trunk.
I get :
pnet.cpp ..\..\..\external\boost\boost/chrono/duration.hpp(94): error: expected an expression && (boost::is_convertible ^
..\..\..\external\boost\boost/chrono/duration.hpp(124): error: expected an expression && (boost::is_convertible ^
compilation aborted for ..\network\pnet.cpp (code 2)
call "C:\Program Files (x86)\Intel\ComposerXE-2011\bin\intel64//iclvars.bat" > nul icl @"bin\intel-win\release\threading-multi\pnet.obj.rsp"
Any suggestions welcome.
Hi,
I have no idea of what could be the cause of the error.
Please could you try adding the namespace boost to common_type and send me the preprocesed output.
Thanks, Vicente
Hi,
I tried adding the namespace boost to common_type on L93,L95,L123 and
L125
but the exact same error appears. Any other ideas?
Hi,
It seems that this compiler version doesn't likes the default bool template initialization with &&.
Could you try if naming the parameter change something? If not could you try to move the default initialization of bool at the template instantiation (line 110)?
Hoping this time is better, Vicente
-- View this message in context: http://boost.2283326.n4.nabble.com/Re-chrono-Can-not-build-with-intel-win-tp... Sent from the Boost - Users mailing list archive at Nabble.com.
Assuming I did it correctly, neither suggestion worked (exact same error message). It does look like Intel doesn't support the && when used in a template initialization. Are you able to propose any other workaround? I will see if I can come up with a simple case where Visual Studio works but Intel doesn't work so that I can post it on Intel Premier support, but a fix for this will take months to appear in a release. Regards, Edward