Re: [boost] Configuration for Intel compiler

2003-05-14 Thread Richard Hadsell
Guillaume Melquiond wrote: Yes, this time the conditional is correct. Unfortunately, this patch is still not good: __ICL is not defined so it doesn't work. My version of the compiler (the standard version available on Intel's website) does not define __ICL, but only __ICC and __INTEL_COMPILER. So

Re: [boost] Configuration for Intel compiler

2003-05-14 Thread Guillaume Melquiond
On Wed, 14 May 2003, Peter Dimov wrote: > Guillaume Melquiond wrote: > > Your patch does not fix the problem at all. In my opinion, it can even > > break some working configurations. I would rather use this > > conditional expression: > > > > # if !(defined(_GLOBAL_USING) && (_GLOBAL_USING+0 >

Re: [boost] Configuration for Intel compiler

2003-05-14 Thread Guillaume Melquiond
On Wed, 14 May 2003, John Maddock wrote: > > Your patch does not fix the problem at all. > > Ah, I see I got the Intel version check backwards, fixed (hopefully!) Yes, this time the conditional is correct. Unfortunately, this patch is still not good: __ICL is not defined so it doesn't work. My ve

Re: [boost] Configuration for Intel compiler

2003-05-14 Thread Peter Dimov
Guillaume Melquiond wrote: > On Tue, 13 May 2003, John Maddock wrote: > >>> One of the first things the configuration header does is: >>> >>> #if !(defined(_GLOBAL_USING) && (_GLOBAL_USING+0 > 0)) && >>> !defined(_STD) # define BOOST_NO_STDC_NAMESPACE >>> #endif >>> >>> However, during comp

Re: [boost] Configuration for Intel compiler

2003-05-14 Thread John Maddock
> Your patch does not fix the problem at all. Ah, I see I got the Intel version check backwards, fixed (hopefully!) > In my opinion, it can even > break some working configurations. I would rather use this conditional > expression: > > # if !(defined(_GLOBAL_USING) && (_GLOBAL_USING+0 > 0 || _C

Re: [boost] Configuration for Intel compiler

2003-05-11 Thread Guillaume Melquiond
On Sun, 11 May 2003, Guillaume Melquiond wrote: > The default configuration defines BOOST_NO_STDC_NAMESPACE for this > compiler. So the library expects to find standard C math functions (the > ones in ) in the global namespace. Unfortunately, they are where > they are supposed to be: in the std na

[boost] Configuration for Intel compiler

2003-05-11 Thread Guillaume Melquiond
Hi, I found a bug in the interval library. but when I corrected it, I stumbled over another problem: this bug was ironically what allowed the library to be correctly compiled with my version of the compiler (Intel compiler 7.1 for Linux). When I remove it, the library no longer works... The defau