Error 1: private field

Member Site Forums Rosetta 3 Rosetta 3 – Build/Install Error 1: private field

Viewing 2 reply threads
  • Author
    Posts
    • #3143
      Anonymous

        Dear All,

        I met such kind of error informaiton when I tried to excute the Rosetta in my mac pro by running the command “rosetta.build_phenix_interface nproc=2” .

        Can anyone tell me how to solve this issue?

        Many thanks.

        Liang

        clang++ -o build/src/release/macos/18.5/64/x86/clang/10.0/python/protocols/match/output/PDBWriter.os -c -std=c++11 -isystem external/boost_1_55_0/ -isystem external/ -isystem external/include/ -isystem external/dbio/ -march=core2 -mtune=generic -pipe -Qunused-arguments -DUNUSUAL_ALLOCATOR_DECLARATION -ftemplate-depth-256 -stdlib=libstdc++ -W -Wall -Wextra -pedantic -Werror -Wno-long-long -Wno-strict-aliasing -march=native -mtune=native -stdlib=libc++ -Wno-unused-variable -O3 -Wno-unused-variable -Wno-unused-parameter -fPIC -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_MATH_NO_LONG_DOUBLE_MATH_FUNCTIONS -DPTR_STD -DNDEBUG -DWITH_PYTHON=1 -Isrc -Iexternal/include -Isrc/platform/macos/64/clang/10.0 -Isrc/platform/macos/64/clang -Isrc/platform/macos/64 -Isrc/platform/macos -Iexternal/boost_1_55_0 -Iexternal/libxml2/include -Iexternal -Iexternal/dbio -I/usr/include -I/usr/local/include -Iexternal/include/python2.7 src/protocols/match/output/PDBWriter.cc

        In file included from src/protocols/mpi_refinement/WorkUnit_Loop.cc:15:

        src/protocols/mpi_refinement/WorkUnit_Loop.hh:140:7: error: private field

              ‘kicclose_’ is not used [-Werror,-Wunused-private-field]

                bool kicclose_;

                     ^

        1 error generated.

        scons: *** [build/src/release/macos/18.5/64/x86/clang/10.0/python/protocols/mpi_refinement/WorkUnit_Loop.os] Error 1

        scons: building terminated because of errors.

      • #14705
        Anonymous

          The error you’re seeing is due to increased compiler checks we’ve added for development purposes. The downsides of them are that they can be noisy on different platform/compiler combinations. For recent versions of Rosetta, we’ve set things up such that these extra checks are disabled for the released versions.

          There’s two potential fixes. The first is to get a more recent version of Rosetta.

          If updating the version of Rosetta isn’t something you’re interested in, you can turn off the “Werror” settings in your site.settings or user.settings file. The file Rosetta/main/source/tools/build/site.settings.tacc.stampede is *almost* what you need. Simply copy that file to Rosetta/main/source/tools/build/site.settings and use a text editor to remove the cxx and cc lines in the “overrides” block. — The other option is to go through the file Rosetta/main/source/tools/build/basic.settings and delete all the lines with “Werror” in them.

        • #14721
          Anonymous

            Dear Rmoretti,

            Thanks for your reply and great suggestions. Indeed the version I installed should be the updated version. Anyway, when I removed “Werror”  from Rosetta/main/source/tools/build/basic.settings, it works !!

            Thanks a lot !!!

            Liang

             

            • #14722
              Anonymous

                I’m a little surprised that a recent version of Rosetta doesn’t have that turned off.

                If you wouldn’t mind, I’d appreciate knowing which version of Rosetta you’re using, so I can take a closer look at what might have gone wrong.

              • #14724
                Anonymous

                  Dear Rmoretti,

                  I think I installed this version: Rosetta 3.10 source + binaries for Mac – as one bundle (9.3G).

                  However, I checked the folder, and name of the folder is: rosetta_bin_mac_2017.08.59291_bundle….

                  Best,

                  Liang

                   

                   

                   

            Viewing 2 reply threads
            • You must be logged in to reply to this topic.