Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-19746

3.0.5 fails to build without c++11

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.0.5
    • Component/s: Build
    • None
    • ALL
    • Hide

      Try to build:

      scons all -j4 --use-system-all --variant-dir=build.fc23 --nostrip --ssl --disable-warnings-as-errors --wiredtiger=on

      with

      $ gcc --version
gcc (GCC) 5.1.1 20150618 (Red Hat 5.1.1-4)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
      Show
      Try to build: scons all -j4 --use-system-all --variant-dir=build.fc23 --nostrip --ssl --disable-warnings-as-errors --wiredtiger=on with $ gcc --version gcc (GCC) 5.1.1 20150618 (Red Hat 5.1.1-4) Copyright (C) 2015 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
    • Platform 9 (09/18/15), Platform A (10/09/15)

      Mongodb 3.0.5 uses keyword "auto" from this commit.
      And this keyword change meaning in c++11 standard. So compilation fails with this error:

      src/mongo/shell/bench.cpp: In member function 'void mongo::BenchRunWorker::generateLoadOnConnection(mongo::DBClientBase*)':
src/mongo/shell/bench.cpp:379:17: warning: 'auto' changes meaning in C++11; please remove it [-Wc++0x-compat]
                 auto& stats = shouldCollectStats() ? _stats : _statsBlackHole;
                 ^

      See attached build.log

        1. build.log
          157 kB
          Marek Skalický

            Assignee:
            andrew.morrow@mongodb.com Andrew Morrow (Inactive)
            Reporter:
            mskalick Marek Skalický
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: