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

Build Error error: static assertion failed: Failed to reserve enough space in fc::fwd<T,S> #1935

Closed
kimziv opened this issue Aug 18, 2019 · 9 comments · Fixed by bitshares/bitshares-fc#150
Labels
3d Bug Classification indicating the existing implementation does not match the intention of the design 6 Build Impact flag identifying the build process

Comments

@kimziv
Copy link

kimziv commented Aug 18, 2019

Instructions
Please include a detailed Title above. Next, please complete the following sections below:

  • Build Error
    In file included from /root/bitshares-core/libraries/fc/src/network/tcp_socket.cpp:4:0:
    /root/bitshares-core/libraries/fc/include/fc/fwd_impl.hpp: In instantiation of ‘void fc::check_size() [with long unsigned int RequiredSize = 96ul; long unsigned int ProvidedSize = 84ul]’:
    /root/bitshares-core/libraries/fc/include/fc/fwd_impl.hpp:85:43: required from ‘fc::fwd<T, S, Align>::fwd() [with T = fc::tcp_socket::impl; unsigned int S = 84u; Align = double]’
    /root/bitshares-core/libraries/fc/src/network/tcp_socket.cpp:91:26: required from here
    /root/bitshares-core/libraries/fc/include/fc/fwd_impl.hpp:60:25: error: static assertion failed: Failed to reserve enough space in fc::fwd<T,S>
    void check_size() { static_assert( (ProvidedSize >= RequiredSize), "Failed to reserve enough space in fc::fwd<T,S>" ); }
    ^
    libraries/fc/CMakeFiles/fc.dir/build.make:816: recipe for target 'libraries/fc/CMakeFiles/fc.dir/src/network/tcp_socket.cpp.o' failed
    make[2]: *** [libraries/fc/CMakeFiles/fc.dir/src/network/tcp_socket.cpp.o] Error 1
    CMakeFiles/Makefile2:183: recipe for target 'libraries/fc/CMakeFiles/fc.dir/all' failed
    make[1]: *** [libraries/fc/CMakeFiles/fc.dir/all] Error 2
    Makefile:129: recipe for target 'all' failed

Build Error Description
error: static assertion failed: Failed to reserve enough space in fc::fwd<T,S>
my os is ubuntu 16.04
when build test-3.3.0 and test-3.3.1 , the same build error occured.

help!

@kimziv kimziv changed the title error: static assertion failed: Failed to reserve enough space in fc::fwd<T,S> Build Error error: static assertion failed: Failed to reserve enough space in fc::fwd<T,S> Aug 18, 2019
@pmconrad pmconrad added 3d Bug Classification indicating the existing implementation does not match the intention of the design 4d Critical Priority Priority indicating system stoppage may occur and no workaround exists 6 Build Impact flag identifying the build process labels Aug 19, 2019
@pmconrad pmconrad added this to To do in Feature Release (3.3.0) via automation Aug 19, 2019
@pmconrad pmconrad added this to the 3.3.0 - Feature Release milestone Aug 19, 2019
@pmconrad
Copy link
Contributor

@kimziv please fill in all fields of the report template, we're asking for that information for a reason.

AFAIK nobody has seen this error on ubuntu-16.04 yet. Which compiler and boost version are you using?

@kimziv
Copy link
Author

kimziv commented Aug 19, 2019

thanks

@oxarbitrage
Copy link
Member

@kimziv what boost version are you using ?

i just built in ubuntu 16.04 with boost 1.58 without problems.

also, can you check if bitshares/bitshares-fc#150 fix the issue for you ? You can just insert the changed code manually(https://github.com/bitshares/bitshares-fc/pull/150/files) and rebuild.

Thank you.

@kimziv
Copy link
Author

kimziv commented Aug 19, 2019

@kimziv what boost version are you using ?

i just built in ubuntu 16.04 with boost 1.58 without problems.

also, can you check if bitshares/bitshares-fc#150 fix the issue for you ? You can just insert the changed code manually(https://github.com/bitshares/bitshares-fc/pull/150/files) and rebuild.

Thank you.

you are right , my boost version is 1.70

@pmconrad
Copy link
Contributor

my boost version is 1.70

Thanks for the info. We do not officially support Boost-1.70 yet, please use a version between 1.58 and 1.69 (1.58 is standard in Ubuntu-16.04 and should work just fine).

Removing the "Critical" label, I think we don't need to create a new testnet release for this.

@pmconrad pmconrad removed the 4d Critical Priority Priority indicating system stoppage may occur and no workaround exists label Aug 20, 2019
@abitmore
Copy link
Member

Move it to next release? Or we still want it for 3.3.0 mainnet release?

@pmconrad
Copy link
Contributor

IMO move to next one. That gives us time to test 1.70 properly and perhaps document official support.

@abitmore
Copy link
Member

Will manually close after bumped FC.

@abitmore abitmore reopened this Aug 20, 2019
Protocol Upgrade Release (5.0.0) automation moved this from Done to To do Aug 20, 2019
@pmconrad
Copy link
Contributor

FC bumped in #1946

Protocol Upgrade Release (5.0.0) automation moved this from To do to Done Aug 21, 2019
@pmconrad pmconrad removed this from the 4.1.0 - Feature Release milestone Oct 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3d Bug Classification indicating the existing implementation does not match the intention of the design 6 Build Impact flag identifying the build process
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

4 participants