Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fails to build with Boost 1.69 (develop snapshot) #2308

Closed
jbeich opened this issue Oct 26, 2018 · 6 comments
Closed

Fails to build with Boost 1.69 (develop snapshot) #2308

jbeich opened this issue Oct 26, 2018 · 6 comments
Labels
category:bug The Issue/PR describes or solves a perceived malfunction within the game. component:internal The Issue/PR deals with any project component that has no explicit `component` label. status:resolved The Issue was resolved, either by answering properly or fixing the underlying bug.
Milestone

Comments

@jbeich
Copy link
Contributor

jbeich commented Oct 26, 2018

After boostorg/boost#189 build fails, see error log and missing files

CMake Error at /usr/local/share/cmake/Modules/FindBoost.cmake:2049 (message):
  Unable to find the requested Boost libraries.

  Boost version: 1.69.0

  Boost include path: /usr/local/include

  Could not find the following Boost libraries:

          boost_signals

Note, according to Boost calendar 1.69 release is planned sometime in December.

@o01eg
Copy link
Contributor

o01eg commented Oct 26, 2018

Looks like it will affect 0.4.8 as well.

@geoffthemedio geoffthemedio added category:bug The Issue/PR describes or solves a perceived malfunction within the game. component:internal The Issue/PR deals with any project component that has no explicit `component` label. labels Oct 26, 2018
@geoffthemedio
Copy link
Member

geoffthemedio commented Oct 26, 2018

I thought the signals dependency was removed some time ago. Does this just require a change to a CMakeLists.txt ? Perhaps to change a default from signals to signals2 ?

@Vezzra Vezzra added this to the Next Release milestone Nov 1, 2018
@Vezzra
Copy link
Member

Vezzra commented Nov 1, 2018

Has this been fixed sufficiently by #2310? Can we close it as resolved?

@geoffthemedio
Copy link
Member

Seemingly yes

#2310 (comment)

@geoffthemedio geoffthemedio added the status:resolved The Issue was resolved, either by answering properly or fixing the underlying bug. label Nov 4, 2018
@jbeich
Copy link
Contributor Author

jbeich commented Nov 26, 2018

After boostorg/serialization@af46ac2da3e9 (post-Beta1) build fails. See error log. Including <string> just after <memory> in combat/CombatEvent.h appears to be enough to fix it.

In file included from combat/CombatEvent.cpp:1:
combat/CombatEvent.h:42:25: error: implicit instantiation of undefined template 'std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >'
    virtual std::string CombatLogDetails(int viewing_empire_id) const
                        ^
/usr/include/c++/v1/iosfwd:193:32: note: template is declared here
    class _LIBCPP_TEMPLATE_VIS basic_string;
                               ^
In file included from combat/CombatEvent.cpp:1:
combat/CombatEvent.h:43:14: error: implicit instantiation of undefined template 'std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >'
    { return std::string(""); }
             ^
/usr/include/c++/v1/iosfwd:193:32: note: template is declared here
    class _LIBCPP_TEMPLATE_VIS basic_string;
                               ^

@geoffthemedio
Copy link
Member

As in that pull request?

geoffthemedio added a commit that referenced this issue Nov 27, 2018
Include to address Boost build issue in comment: #2308 (comment)
@Vezzra Vezzra modified the milestones: Next Release, v0.4.9 Sep 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:bug The Issue/PR describes or solves a perceived malfunction within the game. component:internal The Issue/PR deals with any project component that has no explicit `component` label. status:resolved The Issue was resolved, either by answering properly or fixing the underlying bug.
Projects
None yet
Development

No branches or pull requests

4 participants