Error while compiling Rosetta 3.2. on Ubuntu 11.04 (AMD64)

Member Site › Forums › Rosetta 3 › Rosetta 3 – Build/Install › Error while compiling Rosetta 3.2. on Ubuntu 11.04 (AMD64)

  • This topic has 1 reply, 2 voices, and was last updated 13 years ago by Anonymous.
Viewing 1 reply thread
  • Author
    Posts
    • July 6, 2011 at 3:47 pm #969
      Anonymous

        Hi,

        I am trying to build Rosetta 3.2 on my ubuntu box through scon. After modifying the source in accordance with htt-DNDEBUG -Isrc -Iexternal/include -Isrc/platform/linux/64/gcc/4.5 -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/jd2/archive/ArchiveManager.cc
        {standard input}: Assembler messages:
        {standard input}:535948: Warning: end of file in string; ‘”‘ inserted
        g++: Internal error: Killed (program cc1plus)
        Please submit a full bug report.
        See for instructions.
        scons: *** [build/src/release/linux/2.6/64/x86/gcc/4.5/protocols/jd2/archive/ArchiveManager.os] Error 1
        scons: building terminated because of errors.
        p://morganbye.net/blog/2011/05/rosetta-32-ubuntu-1104, the build process halted with the following error:


        -DNDEBUG -Isrc -Iexternal/include -Isrc/platform/linux/64/gcc/4.5 -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/jd2/archive/ArchiveManager.cc
        {standard input}: Assembler messages:
        {standard input}:535948: Warning: end of file in string; '"' inserted
        g++: Internal error: Killed (program cc1plus)
        Please submit a full bug report.
        See for instructions.
        scons: *** [build/src/release/linux/2.6/64/x86/gcc/4.5/protocols/jd2/archive/ArchiveManager.os] Error 1
        scons: building terminated because of errors.

        Any thoughts?

        Thanks

      • July 6, 2011 at 5:57 pm #5838
        Anonymous

          It has been our experience that gcc internal compiler errors are due to the very high inline limit; there are some instructions on lowering the inline limit here:

          https://www.rosettacommons.org/node/2274

          I have no idea if it will work but it’s worth a shot.

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