Rosetta 3.2.1 CentOS-5 x86_64 gcc: “scons cat=test mode=release” failure

Member Site Forums Rosetta 3 Rosetta 3 – Build/Install Rosetta 3.2.1 CentOS-5 x86_64 gcc: “scons cat=test mode=release” failure

Viewing 3 reply threads
  • Author
    Posts
    • #854
      Anonymous

        python 2.4
        scons 2.0.1
        gcc 4.1.2 (CentOS-5 version)


        [tru@liberte rosetta_source]$ scons -j8 bin mode=release
        ...

        finished fine …

        but testing fails:

        [tru@liberte rosetta_source]$ scons -j8 cat=test mode=release
        scons: Reading SConscript files ...
        svn: '.' is not a working copy

        scons: warning: The build_dir keyword has been deprecated; use the variant_dir keyword instead.
        File "/c5/shared/rosetta/3.2.1/rosetta_source/SConscript", line 40, in ?

        scons: warning: The build_dir keyword has been deprecated; use the variant_dir keyword instead.
        File "/c5/shared/rosetta/3.2.1/rosetta_source/SConscript", line 40, in ?

        scons: warning: The build_dir keyword has been deprecated; use the variant_dir keyword instead.
        File "/c5/shared/rosetta/3.2.1/rosetta_source/SConscript", line 40, in ?

        scons: warning: The build_dir keyword has been deprecated; use the variant_dir keyword instead.
        File "/c5/shared/rosetta/3.2.1/rosetta_source/SConscript", line 40, in ?

        scons: warning: The build_dir keyword has been deprecated; use the variant_dir keyword instead.
        File "/c5/shared/rosetta/3.2.1/rosetta_source/SConscript", line 40, in ?

        scons: warning: The build_dir keyword has been deprecated; use the variant_dir keyword instead.
        File "/c5/shared/rosetta/3.2.1/rosetta_source/SConscript", line 40, in ?

        scons: warning: The build_dir keyword has been deprecated; use the variant_dir keyword instead.
        File "/c5/shared/rosetta/3.2.1/rosetta_source/SConscript", line 40, in ?
        scons: done reading SConscript files.
        scons: Building targets ...
        scons: *** [build/test/release/linux/2.6/64/x86/gcc/devel/devel.cxxtest.cpp] Source `test/devel/devel.cxxtest.hh' not found, needed by target `build/test/release/linux/2.6/64/x86/gcc/devel/devel.cxxtest.cpp'.
        scons: building terminated because of errors.

      • #5287
        Anonymous

          I also tried:
          [tru@liberte rosetta_source]$ scons cat=test
          ...
          external/cxxtest/cxxtestgen.py --have-std --part -o build/test/debug/linux/2.6/64/x86/gcc/core/util/MetricValueIO.cxxtest.cpp test/core/util/MetricValueIO.cxxtest.hh
          g++ -o build/test/debug/linux/2.6/64/x86/gcc/core/util/MetricValueIO.cxxtest.o -c -std=c++98 -pipe -ffor-scope -W -Wall -pedantic -Wno-long-long -O0 -g -ggdb -ffloat-store -Iexternal/cxxtest -I. -Itest -Isrc -Iexternal/include -Isrc/platform/linux/64/gcc -Isrc/platform/linux/64 -Isrc/platform/linux -Iexternal/boost_1_38_0 -I/usr/local/include -I/usr/include build/test/debug/linux/2.6/64/x86/gcc/core/util/MetricValueIO.cxxtest.cpp
          scons: *** [build/test/debug/linux/2.6/64/x86/gcc/devel/devel.cxxtest.cpp] Source `test/devel/devel.cxxtest.hh' not found, needed by target `build/test/debug/linux/2.6/64/x86/gcc/devel/devel.cxxtest.cpp'.
          scons: building terminated because of errors.

        • #5288
          Anonymous

            I suspect you are the only person in the world to have ever tried to compile the 3.2.x release’s tests at all – this is not a centos problem.

            The devel/ part of the code is reserved by the developers and does not get released; sometimes we fail to remove all references to it in the released code.

            If you just remove the file devel.test.settings from the test/ folder, it will work fine (spitting a warning about missing code).

            You will also need to delete the line including “devel/init.hh” in the files
            ./test/numeric/interpolation/spline/Bicubic_spline.cxxtest.hh
            ./test/numeric/interpolation/spline/Cubic_spline.cxxtest.hh

          • #5289
            Anonymous

              The latter problem is now fixed in trunk. (The original problem doesn’t exist in trunk, so I can’t fix it.)

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