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

Debug build fails in configure

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.11
    • Affects Version/s: None
    • Component/s: Build
    • None
    • Fully Compatible
    • ALL
    • Hide

      My build command:

      python27 scons --wiredtiger --dbg=on -j 24 core
      

      The error:

      Checking for C library wpcap... no
      Checking if std::atomic<int64_t> works... no
      Checking for C library atomic... yes
      Checking if std::atomic<int64_t> works with libatomic... no
      The toolchain does not support std::atomic, cannot continue
      See /mnt/fast/sue/work/mongo/build/scons/config.log for details
      

      And the details from config.log:

      scons: Configure: Checking if std::atomic<int64_t> works with libatomic...
      build/scons/sconf_temp/conftest_53.cpp <-
        |
        |#include <atomic>
        |
        |int main() {
        |    std::atomic<int64_t> x;
        |
        |    x.store(0);
        |    int64_t y = 1;
        |    x.fetch_add(y);
        |    x.fetch_sub(y);
        |    x.exchange(y);
        |    x.compare_exchange_strong(y, x);
        |    return x.load();
        |}
        |
      Compiling build/scons/sconf_temp/conftest_53.o
      In file included from /opt/mongodbtoolchain/v2/include/c++/5.3.0/x86_64-mongodb-linux/bits/os_defines.h:39:0,
                       from /opt/mongodbtoolchain/v2/include/c++/5.3.0/x86_64-mongodb-linux/bits/c++config.h:482,
                       from /opt/mongodbtoolchain/v2/include/c++/5.3.0/bits/atomic_base.h:35,
                       from /opt/mongodbtoolchain/v2/include/c++/5.3.0/atomic:41,
                       from build/scons/sconf_temp/conftest_53.cpp:2:
      /usr/include/features.h:330:4: error: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Werror=cpp]
       #  warning _FORTIFY_SOURCE requires compiling with optimization (-O)
          ^
      cc1plus: all warnings being treated as errors
      scons: Configure: no
      
      Show
      My build command: python27 scons --wiredtiger --dbg=on -j 24 core The error: Checking for C library wpcap... no Checking if std::atomic<int64_t> works... no Checking for C library atomic... yes Checking if std::atomic<int64_t> works with libatomic... no The toolchain does not support std::atomic, cannot continue See /mnt/fast/sue/work/mongo/build/scons/config.log for details And the details from config.log: scons: Configure: Checking if std::atomic<int64_t> works with libatomic... build/scons/sconf_temp/conftest_53.cpp <- | |#include <atomic> | |int main() { | std::atomic<int64_t> x; | | x.store(0); | int64_t y = 1; | x.fetch_add(y); | x.fetch_sub(y); | x.exchange(y); | x.compare_exchange_strong(y, x); | return x.load(); |} | Compiling build/scons/sconf_temp/conftest_53.o In file included from /opt/mongodbtoolchain/v2/include/c++/5.3.0/x86_64-mongodb-linux/bits/os_defines.h:39:0, from /opt/mongodbtoolchain/v2/include/c++/5.3.0/x86_64-mongodb-linux/bits/c++config.h:482, from /opt/mongodbtoolchain/v2/include/c++/5.3.0/bits/atomic_base.h:35, from /opt/mongodbtoolchain/v2/include/c++/5.3.0/atomic:41, from build/scons/sconf_temp/conftest_53.cpp:2: /usr/include/features.h:330:4: error: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Werror=cpp] # warning _FORTIFY_SOURCE requires compiling with optimization (-O) ^ cc1plus: all warnings being treated as errors scons: Configure: no
    • Platforms 18 (08/05/16)

      When attempting to build a debug version with --dbg=on from master, it fails in configure. mark.benvenuto gave me a workaround, adding --dbg=on --runtime-hardening=off makes it work and complete.

      I'm building on AWS linux. Mark saw it using GCC 5.3 on master as well.

            Assignee:
            waley.chen Waley Chen
            Reporter:
            sue.loverso@mongodb.com Susan LoVerso
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: