Bug #6199
closedError building Wt 4 with Boost 1.66
0%
Description
Hi Witty devs,
Using debian testing with latest packages; building with GCC 7.2 and Boost 1.66, I get the following errors:
[ 66%] Building CXX object src/CMakeFiles/wt.dir/Wt/Http/Response.C.o
In file included from /home/marco/Development/wt-4.0.2/src/Wt/Http/Client.C:10:0:
/home/marco/Development/wt-4.0.2/src/Wt/Http/Client.h:26:11: error: using typedef-name ‘boost::asio::io_service’ after ‘class’
class io_service;
^~~~~~~~~~
In file included from /home/marco/local/include/boost/asio.hpp:69:0,
from /home/marco/Development/wt-4.0.2/src/Wt/AsioWrapper/asio.hpp:14,
from /home/marco/Development/wt-4.0.2/src/Wt/Http/Client.C:8:
/home/marco/local/include/boost/asio/io_service.hpp:27:20: note: ‘boost::asio::io_service’ has a previous declaration here
typedef io_context io_service;
^~~~~~~~~~
[ 66%] Building CXX object src/CMakeFiles/wt.dir/Wt/Http/ResponseContinuation.C.o
/home/marco/Development/wt-4.0.2/src/Wt/Http/Client.C:645:3: error: invalid use of template-name ‘boost::asio::strand’ without an argument list
asio::strand strand_;
^~~~
/home/marco/Development/wt-4.0.2/src/Wt/Http/Client.C:645:3: note: class template argument deduction is only available with -std=c++1z or -std=gnu++1z
In file included from /home/marco/local/include/boost/asio.hpp:123:0,
from /home/marco/Development/wt-4.0.2/src/Wt/AsioWrapper/asio.hpp:14,
from /home/marco/Development/wt-4.0.2/src/Wt/Http/Client.C:8:
/home/marco/local/include/boost/asio/strand.hpp:29:7: note: ‘template<class Executor> class boost::asio::strand’ declared here
class strand
I had a quick look at the files where the errors are coming from and it appears the root cause is that Boost Asio has defined these as typedefs, and Wt is forward declaring them.
Cheers
Updated by Roel Standaert almost 7 years ago
- Status changed from New to Resolved
This has already been resolved on the master branch.
Updated by Simon M over 6 years ago
Roel Standaert wrote:
This has already been resolved on the master branch.
Hi,
I ran into this issue, when building 4.0.2 today.
Do I need to use sources from master or is there a new bugfix release anticipated?
thanks
Updated by Simon M over 6 years ago
Ok, so I assume this was the fix: https://github.com/emweb/wt/commit/960e8d017b264710e344c63f9feb6ea1fa593eeb which was after 4.0.2.
I'm currently building from master, let's see, if it now works.
Would it make sense to release a new bugfix release? 4.0.2 is already 4 months old.
Updated by Wim Dumon over 6 years ago
We're preparing a release now, if all goes well it the release candidate will be available before the end of the week.
Wim.
Updated by Roel Standaert over 6 years ago
- Status changed from Resolved to Closed