compile thread(boost1.55) fail on vc7.1

*bjam toolset=msvc-7.1 link=static threading=multi runtime-link=static
--with-thread --with-chrono --with-date_time --includedir=hpp stage*>err.txt
Component configuration:
- atomic : not building
- chrono : building
- context : not building
- coroutine : not building
- date_time : building
- exception : not building
- filesystem : not building
- graph : not building
- graph_parallel : not building
- iostreams : not building
- locale : not building
- log : not building
- math : not building
- mpi : not building
- program_options : not building
- python : not building
- random : not building
- regex : not building
- serialization : not building
- signals : not building
- system : not building
- test : not building
- thread : building
- timer : not building
- wave : not building
...patience...
...patience...
...found 1497 targets...
...updating 6 targets...
compile-c-c++
bin.v2\libs\thread\build\msvc-7.1\debug\link-static\runtime-link-static\threading-multi\win32\thread.obj
thread.cpp
boost\functional\hash\hash.hpp(32) : warning C4616: #pragma warning :
警告编号“6295”超出范围,必须在“4001”和“4999“之间
boost\thread\future.hpp(1488) : error C2039:
“make_future_async_shared_state” : 不是“boost::detail”的成员
boost\thread\future.hpp(1638) :
参见对正在编译的类模板实例化“boost::unique_future<R>”的引用
boost\thread\future.hpp(1492) : error C2039:
“make_future_deferred_shared_state” : 不是“boost::detail”的成员
boost\thread\future.hpp(1683) : error C2039:
“make_future_async_shared_state” : 不是“boost::detail”的成员
boost\thread\future.hpp(1807) :
参见对正在编译的类模板实例化“boost::unique_future

On Nov 11, 2013, at 11:25 PM, shada
*bjam toolset=msvc-7.1 link=static threading=multi runtime-link=static --with-thread --with-chrono --with-date_time --includedir=hpp stage*>err.txt
[ Error transcript snipped ] A bit from the 1.55.0 release notes: Support was removed from Config for some very old versions of compilers. The new minimum requirements are: • Digitial Mars 8.41 • GCC 3.3 • Intel 6.0 • Visual C++ 7.1 -- Marshall Marshall Clow Idio Software mailto:mclow.lists@gmail.com A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki

On Tue, Nov 12, 2013 at 06:08:22AM -0800, Marshall Clow wrote:
On Nov 11, 2013, at 11:25 PM, shada
wrote: *bjam toolset=msvc-7.1 link=static threading=multi runtime-link=static --with-thread --with-chrono --with-date_time --includedir=hpp stage*>err.txt
[ Error transcript snipped ]
A bit from the 1.55.0 release notes:
Support was removed from Config for some very old versions of compilers. The new minimum requirements are:
• Digitial Mars 8.41 • GCC 3.3 • Intel 6.0 • Visual C++ 7.1
Barring typos, isn't he just inside the range of acceptable compilers? -- Lars Viklund | zao@acc.umu.se

On 12 November 2013 14:18, Lars Viklund
On Tue, Nov 12, 2013 at 06:08:22AM -0800, Marshall Clow wrote:
On Nov 11, 2013, at 11:25 PM, shada
wrote: *bjam toolset=msvc-7.1 link=static threading=multi runtime-link=static --with-thread --with-chrono --with-date_time --includedir=hpp stage*>err.txt
[ Error transcript snipped ]
A bit from the 1.55.0 release notes:
Support was removed from Config for some very old versions of compilers. The new minimum requirements are:
• Digitial Mars 8.41 • GCC 3.3 • Intel 6.0 • Visual C++ 7.1
Barring typos, isn't he just inside the range of acceptable compilers?
Yes.

On Nov 12, 2013, at 6:18 AM, Lars Viklund
On Tue, Nov 12, 2013 at 06:08:22AM -0800, Marshall Clow wrote:
On Nov 11, 2013, at 11:25 PM, shada
wrote: *bjam toolset=msvc-7.1 link=static threading=multi runtime-link=static --with-thread --with-chrono --with-date_time --includedir=hpp stage*>err.txt
[ Error transcript snipped ]
A bit from the 1.55.0 release notes:
Support was removed from Config for some very old versions of compilers. The new minimum requirements are:
• Digitial Mars 8.41 • GCC 3.3 • Intel 6.0 • Visual C++ 7.1
Barring typos, isn't he just inside the range of acceptable compilers?
D'oh - I completely misread that! Yes, you are correct. -- Marshall Marshall Clow Idio Software mailto:mclow.lists@gmail.com A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki

El 12/11/2013 15:08, Marshall Clow escribió:
On Nov 11, 2013, at 11:25 PM, shada
wrote: *bjam toolset=msvc-7.1 link=static threading=multi runtime-link=static --with-thread --with-chrono --with-date_time --includedir=hpp stage*>err.txt
[ Error transcript snipped ]
A bit from the 1.55.0 release notes:
Support was removed from Config for some very old versions of compilers. The new minimum requirements are:
• Digitial Mars 8.41 • GCC 3.3 • Intel 6.0 • Visual C++ 7.1
So I understand that Visual 7.1 should be supported and the report it's a bug. Ion

On 12 November 2013 16:04, Ion Gaztañaga
El 12/11/2013 15:08, Marshall Clow escribió:
On Nov 11, 2013, at 11:25 PM, shada
wrote: *bjam toolset=msvc-7.1 link=static threading=multi runtime-link=static --with-thread --with-chrono --with-date_time --includedir=hpp stage*>err.txt
[ Error transcript snipped ]
A bit from the 1.55.0 release notes:
Support was removed from Config for some very old versions of compilers. The new minimum requirements are:
• Digitial Mars 8.41 • GCC 3.3 • Intel 6.0 • Visual C++ 7.1
So I understand that Visual 7.1 should be supported and the report it's a bug.
It's your choice whether or not you wish to support Visual C++ 7.1.

On Tue, Nov 12, 2013 at 10:04 AM, Ion Gaztañaga
El 12/11/2013 15:08, Marshall Clow escribió:
On Nov 11, 2013, at 11:25 PM, shada
wrote: *bjam toolset=msvc-7.1 link=static threading=multi runtime-link=static
--with-thread --with-chrono --with-date_time --includedir=hpp stage*>err.txt
[ Error transcript snipped ]
A bit from the 1.55.0 release notes:
Support was removed from Config for some very old versions of compilers. The new minimum requirements are:
• Digitial Mars 8.41 • GCC 3.3 • Intel 6.0 • Visual C++ 7.1
So I understand that Visual 7.1 should be supported and the report it's a bug.
It is in the supported list, but if you look further down, there are no tests running against 7.1. I guess this means we'll accept bugs against it but make no claims to its being able to run out of the box? Tom

On 13/11/13 06:31, Tom Kent wrote:
On Tue, Nov 12, 2013 at 10:04 AM, Ion Gaztañaga
wrote: So I understand that Visual 7.1 should be supported and the report it's a bug.
It is in the supported list, but if you look further down, there are no tests running against 7.1. I guess this means we'll accept bugs against it but make no claims to its being able to run out of the box?
Yeah, that sounds right. The list of minimum requirements don't really imply "supported" in the sense that all features of all libraries are expected to work. It means what it says, "Support was removed" for older versions, which, given their age and the reasons for bumping the requirements, means that they won't work. As you said, further down that page (the bottom), primary test compilers and additional test compilers are listed. It's hard to support compilers that are not running tests. Parties interesting in having support for a compiler should consider supporting a test runner for said compiler. On a side note, I don't think Rene meant to add my Clang-3.4 results to the list of primary test compilers as it's not released yet. I'm also testing with gcc-4.8.2 now, although that changed happened late in the release cycle (after the first beta if I recall). Ben
participants (7)
-
Ben Pope
-
Daniel James
-
Ion Gaztañaga
-
Lars Viklund
-
Marshall Clow
-
shada
-
Tom Kent