Tried for you... gcc 4.5.1, Aug 31 gcc 4.6

[vamiot]

These two (gcc 4.5.1 &  4.6) are still having fits with futures/asyncs (bomb at runtime, 4.6 a bit more cleanly)
(local rebuild from sources on (uname -a):
Linux Gypsy-IV 2.6.32-25-server #43-Ubuntu SMP Wed Sep 1 10:54:43 UTC 2010 x86_64 GNU/Linux

Note futures are not even in the C++0x supported/unsupported list, see http://gcc.gnu.org/projects/cxx0x.html (concurrency?), does anyone know?

[Anthony Williams]

The native gcc support in the current trunk for the library facilities such as futures is listed at http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.200x. For a particular version you'll have to check your local copy of that documentation page, as the gcc website doesn't seem to list the support that shipped with each individual version.

[Anthony Williams]

And just for clarity: just::thread does not support g++ 4.5 or later in the current release.

[TA]

And just for clarity: just::thread does not support g++ 4.5 or later in the current release.

Hi Anthony,

Compatible with g++ 4.3, 4.4 and 4.5 for 32-bit and 64-bit Ubuntu linux (x86/x86_64) targets, making full use of the C++0x support from g++ including rvalue references and variadic templates.

http://www.stdthread.co.uk/
On the other hand my documentation said

Compatible with g++ 4.3 and g++ 4.4 for 32-bit and 64-bit Ubuntu linux targets.

Nothing about gcc 4.5.
Which information is more correct?

BTW, readme.txt from my copy says "The just::thread C++ Thread Library v1.0", while there is announcement of V1.3 as a last version
http://www.stdthread.co.uk/forum/index.php/topic,73.0.html
As far as I see that is the latest version, you probably forgot to update readme.txt

Thanks.

[Anthony Williams]

The current release supports gcc 4.5 (if you install the right .debs); older releases did not, and the message was correct when written. I guess I ought to update the readme and documentation.

[TA]

The current release supports gcc 4.5 (if you install the right .debs); older releases did not, and the message was correct when written. I guess I ought to update the readme and documentation.

Thanks.