Rosetta 3.1 seg faults gcc while compiling on Fedora 11

Member Site › Forums › Rosetta 3 › Rosetta 3 – General › Rosetta 3.1 seg faults gcc while compiling on Fedora 11

Viewing 1 reply thread
  • Author
    Posts
    • October 2, 2009 at 12:26 pm #384
      pbradley
      Participant

        uname -a
        Linux vaduz 2.6.30.5-43.fc11.x86_64 #1 SMP Thu Aug 27 21:39:52 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

        gcc –version
        gcc (GCC) 4.4.1 20090725 (Red Hat 4.4.1-2)

        I know it isn’t fully supported but I thought I’d just report it.

        error output

        g++ -o build/src/release/linux/2.6/64/x86/gcc/static/protocols/toolbox/PoseMetricCalculators/ResidueDecompositionCalculator.o -c -std=c++98 -pipe -ffor-scope -W -Wall -pedantic -Wno-long-long -O3 -ffast-math -funroll-loops -finline-functions -finline-limit=20000 -s -Wno-unused-variable -DNDEBUG -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 src/protocols/toolbox/PoseMetricCalculators/ResidueDecompositionCalculator.cc
        src/protocols/toolbox/PoseMetricCalculators/ResidueDecompositionCalculator.cc: In member function ‘void protocols::toolbox::PoseMetricCalculators::ResidueDecompositionCalculator::residue_set_numbers_to_decomposition()’:
        src/protocols/toolbox/PoseMetricCalculators/ResidueDecompositionCalculator.cc:155: internal compiler error: Segmentation fault
        Please submit a full bug report,
        with preprocessed source if appropriate.
        See <http://bugzilla.redhat.com/bugzilla> for instructions.
        Preprocessed source stored into /tmp/ccavOlMA.out file, please attach this to your bugreport.
        scons: *** [build/src/release/linux/2.6/64/x86/gcc/static/protocols/toolbox/PoseMetricCalculators/ResidueDecompositionCalculator.o] Error 1
        scons: building terminated because of errors.

      • October 2, 2009 at 2:02 pm #4211
        Anonymous

          I’ve posted this to the developer’s list to see if anyone else is using 4.4.1 (I think no one is). If someone knows anything it will percolate back to here! (Generally, errors like this are GCC’s fault, not ours, so I don’t know if we can do anything…)

      • Author
        Posts
      Viewing 1 reply thread
      • You must be logged in to reply to this topic.