Build Rosetta – error: ‘build_threading_model’

Member Site › Forums › Rosetta 3 › Rosetta 3 – Build/Install › Build Rosetta – error: ‘build_threading_model’

Viewing 5 reply threads
  • Author
    Posts
    • February 25, 2010 at 4:43 pm #442
      Anonymous

        In order to build a release version of Rosetta executables, I run scons:

        – by Release Mode – scons bin mode=release.

        But I receive this error message:

        src/protocols/loops/LoopRelaxMover.cc: In member function ‘virtual void protocols::loops::LoopRelaxMover::apply(core::pose::Pose&)’:

        src/protocols/loops/LoopRelaxMover.cc:568: error: ‘build_threading_model’ is not a member of ‘core::options::OptionKeys::loops’

        *** [build/src/release/linux/2.6/64/x86/gcc/protocols/loops/LoopRelaxMover.os] Error 1

        Thank you for all.

      • February 25, 2010 at 4:43 pm #4371
        Anonymous

          > In order to build a release version of Rosetta executables, I run scons:
          >
          > – by Release Mode – scons bin mode=release.
          >
          > But I receive this error message:
          >
          > src/protocols/loops/LoopRelaxMover.cc: In member function ‘virtual void protocols::loops::LoopRelaxMover::apply(core::pose::Pose&)’:
          >
          > src/protocols/loops/LoopRelaxMover.cc:568: error: ‘build_threading_model’ is not a member of ‘core::options::OptionKeys::loops’
          >
          > *** [build/src/release/linux/2.6/64/x86/gcc/protocols/loops/LoopRelaxMover.os] Error 1
          >
          > Thank you for all.

        • March 8, 2010 at 5:14 pm #4385
          Anonymous

            What compiler and version are you using? What Python version? Have you made any changes to the code?

            • October 26, 2010 at 12:01 pm #4628
              Anonymous

                I have the same problem with MacOSX 10.4 I tried both 4.0.1 and 4.2.1 g++ versions from Developer tools. Python is 2.6.1 and I use scons from fink. I hope there would be some way to make the compilation to succeed.

            • October 26, 2010 at 3:05 pm #4629
              Anonymous

                Are you actually intending to use the option build_threading_model? If not, try deleting the whole if block it appears in (lines 568-571)

                If you do need that option for whatever reason, try playing with its namespacing. Try a full core::options::OptionKeys::loops::build_threading_model or a using declaration.

                • October 27, 2010 at 10:47 am #4647
                  Anonymous

                    I tried first to use the long namespace, but that didn’t help. Commenting whole thing out did help. When using grep for build_threading_model I didn’t get any other hits so where one would set it if I would like to use it?

                    In any case thank you for your help.

                • October 27, 2010 at 5:16 pm #4650
                  Anonymous

                    I guess the easiest thing if you would like to use it is just make the statement if(true).

                    You could also try swapping it with a different, unused option. I know that all of the AnchoredDesign namespace options are not accessed by any code passing through LoopRelaxMover, so those would be an ok choice for noninterference.

                  • April 13, 2020 at 12:31 am #15238
                    Anonymous

                      I am trying to analyze Protein Sequence via the rstoolbox library but there is a constant error. 

                      On the first run, it gave a Unicode error. In order to avoid this, I changed syntax but it didn’t work. 

                      Now Error is: rossetta_scripts.winccrelease is not found.

                      Please find the attached file for your analysis. 

                      Thank you.

                      • July 9, 2020 at 5:18 pm #15386
                        Anonymous

                          First, since this isn’t a follow on from the other messages in the thread, it’s best to open up a new thread.

                          The Unicode issue is independent of Rosetta. There’s some issue there with your Python and/or Jupyter notebook. (It looks like the issue is actually the fact you’re using backslashes in regular Python strings, which are normally used for escaping. Take a look into Python “raw strings” as a possible solution.)

                          Regarding the “rossetta_scripts.winccrelease is not found” error, that may be a bug in the rstoolbox setup. It may be building the expected Rosetta command name from the current platform, despite the fact that you’re not intending to run Rosetta on the current Windows machine. Since RosettaCommons proper doesn’t maintain or distribute the rstoolbox code, I’d file a bug/open an issue with the rstoolbox maintainers directly.

                    • Author
                      Posts
                    Viewing 5 reply threads
                    • You must be logged in to reply to this topic.