error in compling rosetta in Linux

This topic has 6 replies, 3 voices, and was last updated 7 years, 10 months ago by Anonymous.

Viewing 6 reply threads

Author

Posts
- January 22, 2017 at 10:44 pm #2572
  Anonymous
  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?
- January 23, 2017 at 1:12 am #12109
  Anonymous
  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.
  
  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.
- January 23, 2017 at 1:12 am #12630
  Anonymous
  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.
  
  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.
- January 23, 2017 at 1:12 am #13151
  Anonymous
  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.
  
  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.
- February 28, 2017 at 4:44 pm #12165
  Anonymous
  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”)
- February 28, 2017 at 4:44 pm #12686
  Anonymous
  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”)
- February 28, 2017 at 4:44 pm #13207
  Anonymous
  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”)
Author

Posts

Viewing 6 reply threads

You must be logged in to reply to this topic.