You are here

error in compling rosetta in Linux

3 posts / 0 new
Last post
error in compling rosetta in Linux
#1

Hi I tried to compile rosetta in linux but get this error

 

scons: *** [build/src/release/linux/3.16/32/x86/gcc/4.9/default/protocols/hbnet/HBNet.os] Error 1
src/protocols/hbnet/HBNetStapleInterface.cc: In member function 'virtual void protocols::hbnet::HBNetStapleInterface::setup(core::pose::Pose&)':
src/protocols/hbnet/HBNetStapleInterface.cc:305:35: error: invalid initialization of reference of type 'long unsigned int&' from expression of type 'unsigned int'
   for (unsigned long & jump_num : jump_nums_) {
                                   ^
src/protocols/hbnet/HBNetStapleInterface.cc:346:36: error: invalid initialization of reference of type 'long unsigned int&' from expression of type 'unsigned int'
    for (unsigned long & jump_num : jump_nums_) {
                                    ^
src/protocols/hbnet/HBNetStapleInterface.cc:442:36: error: invalid initialization of reference of type 'long unsigned int&' from expression of type 'unsigned int'
    for (unsigned long & jump_num : jump_nums_) {
                                    ^
src/protocols/hbnet/HBNetStapleInterface.cc: In member function 'void protocols::hbnet::HBNetStapleInterface::rec_add_staple(std::vector<std::shared_ptr<protocols::hbnet::hbond_net_struct> >::const_iterator, std::vector<unsigned int>, utility::pointer::ReferenceCount::Size)':
src/protocols/hbnet/HBNetStapleInterface.cc:723:39: error: invalid initialization of reference of type 'long unsigned int&' from expression of type 'unsigned int'
         for (unsigned long & net_id : net_ids){
                                       ^


How can I solve this?

Category: 
Post Situation: 
Sun, 2017-01-22 14:44
luicui

A) try a different version of Rosetta - if you post the version this is from, and the version you are considering, i can look up if that file is any different.

B) try a different compiler - obviously yours is one we aren't testing against.

C) guessing from the error, you can try converting the "unsigned long &" on those lines to "unsigned int" and seeing if that fixes it.

Sun, 2017-01-22 17:12
smlewis

As an update, this issue has been fixed (because of your bug report!) in the most recent weekly release, 2017.08  

(The fix, if you're not interested in updating wholesale, is to change the "unsigned long" to "core::Size")

Tue, 2017-02-28 08:44
rmoretti