Checking if C++ compiler "g++" is GCC... yes
Checking if C compiler "gcc" is GCC... yes
Detected a arm processor
Checking if target OS linux is supported by the toolchain... yes
Checking if C compiler is GCC 5.3.0 or newer...yes
Checking if C++ compiler is GCC 5.3.0 or newer...yes
Checking if C compiler supports -Wno-unused-local-typedefs... yes
Checking if C compiler supports -Wno-unused-function... yes
Checking if C compiler supports -Wno-unused-private-field... no
Checking if C compiler supports -Wno-deprecated-declarations... yes
Checking if C compiler supports -Wno-tautological-constant-out-of-range-compare... no
Checking if C compiler supports -Wno-tautological-constant-compare... no
Checking if C compiler supports -Wno-tautological-unsigned-zero-compare... no
Checking if C compiler supports -Wno-tautological-unsigned-enum-zero-compare... no
Checking if C compiler supports -Wno-unused-const-variable... yes
Checking if C compiler supports -Wno-unused-but-set-variable... yes
Checking if C compiler supports -Wno-missing-braces... yes
Checking if C compiler supports -Wno-inconsistent-missing-override... no
Checking if C compiler supports -Wno-potentially-evaluated-expression... no
Checking if C++ compiler supports -Wpessimizing-move... no
Checking if C++ compiler supports -Wredundant-move... no
Checking if C++ compiler supports -Wno-maybe-uninitialized... yes
Checking if C++ compiler supports -Wno-undefined-var-template... no
Checking if C++ compiler supports -Wno-instantiation-after-specialization... no
Checking if C compiler supports -Wno-unused-lambda-capture... no
Checking if C compiler supports -Wno-exceptions... no
Checking -Wnon-virtual-dtor for false positives... no
Checking if C compiler supports -fstack-protector-strong... yes
Checking if we are using libstdc++... yes
Checking if C++ compiler supports -std=c++14... yes
Checking if C compiler supports -std=c11... yes
Checking for C++14... yes
Checking for memset_s... no
Checking for C function strnlen()... yes
Checking for libstdc++ 5.3.0 or better... yes
Checking if we are on a POSIX system... yes
Checking if the POSIX monotonic clock is supported... yes
Checking off_t is 8 bytes... no
Checking if linker supports -fuse-ld=gold... yes
Checking if linker supports -Wl,--build-id... yes
Checking if linker supports -Wl,--hash-style=gnu... yes
Checking if linker supports -Wl,-z,noexecstack... yes
Checking if linker supports -Wl,--warn-execstack... yes
Checking if linker supports -Wl,-z,relro... yes
Checking for glibc with non-broken FORTIFY_SOURCE...yes
Checking if C compiler supports -fno-builtin-memcmp... yes
Checking for storage class thread_local yes
Checking for C++14 std::enable_if_t support...yes
Checking for C++14 std::make_unique support... yes
Checking if pthread_setname_np is supported... yes
Checking for SSLeay_version(0) in C library crypto... yes
Checking for SSL_version(NULL) in C library ssl... yes
Checking that linking to OpenSSL works...yes
Checking whether FIPS_mode_set is declared... yes
Checking whether d2i_ASN1_SEQUENCE_ANY is declared... yes
Checking if SSL[CTX_]_set_ecdh_auto is supported... yes
Using SSL Provider: openssl
Checking for curl_global_init(0) in C library curl... yes
Checking for C library rt... yes
Checking for C library dl... yes
Checking for C++ header file execinfo.h... yes
Checking whether backtrace is declared... yes
Checking whether backtrace_symbols is declared... yes
Checking whether backtrace_symbols_fd is declared... yes
Checking for C library pcap... no
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... yes
Checking if std::atomic<uint64_t> works with libatomic... yes
Checking if std::atomic<int32_t> works with libatomic... yes
Checking if std::atomic<uint32_t> works with libatomic... yes
Checking for extended alignment 64 for concurrency types... yes
Checking for mongoc_get_major_version() in C library mongoc-1.0... no
Checking if __malloc_hook is declared volatile... yes
Checking for C function fallocate()... yes
Checking for C function sync_file_range()... yes
Checking for C header file arm_neon.h... yes
scons: done reading SConscript files.
scons: Building targets ...
Compiling build/opt/third_party/IntelRDFPMathLib20U1/LIBRARY/src/bid64_noncomp.o
Compiling build/opt/third_party/IntelRDFPMathLib20U1/LIBRARY/src/bid32_to_bid64.o
/usr/bin/python2 src/mongo/base/generate_error_codes.py src/mongo/base/error_codes.err src/mongo/base/error_codes.tpl.h=build/opt/mongo/base/error_codes.h src/mongo/base/error_codes.tpl.cpp=build/opt/mongo/base/error_codes.cpp
Creating 'build/opt/mongo/config.h'
Compiling build/opt/third_party/boost-1.60.0/libs/filesystem/src/unique_path.o
Compiling build/opt/third_party/icu4c-57.1/source/i18n/rbt_pars.o
Compiling build/opt/mongo/util/signal_handlers_synchronous.o
Compiling build/opt/third_party/gperftools-2.5/src/internal_logging.o
src/third_party/gperftools-2.5/src/internal_logging.cc:34:10: fatal error: config.h: No such file or directory
#include <config.h>
^~~~~~~~~~
compilation terminated.
scons: *** [build/opt/third_party/gperftools-2.5/src/internal_logging.o] Error 1
Compiling build/opt/mongo/db/namespace_string.o
scons: building terminated because of errors.
build/opt/third_party/gperftools-2.5/src/internal_logging.o failed: Error 1

Hi! When I tried to execute sudo ./scripts/build-server.sh first time I got next error:

virtual memory exhausted: Cannot allocate memory
scons: *** [build/opt/mongo/db/repl/master_slave.o] Error 1
scons: building terminated because of errors.
build/opt/mongo/db/repl/master_slave.o failed: Error 1

Then I added swap space, run it again and got one more error:

scons: Build interrupted.
scons: building terminated because of errors.

I use Linux Debian 9.3

Ran the following commands:

sudo ./scripts/build-server.sh r4.0.10
sudo ./scripts/build-tools.sh r4.0.10
sudo cp ./artifacts/root-filesystem/etc/mongodb.conf /etc/mongodb.conf
sudo chmod o-rwx /etc/mongodb.conf
sudo chown mongodb:mongodb /etc/mongodb.conf
sudo systemctl start mongodb-server

Hi!
I use Debian Sid. Additional info if it helps, the result of command "cat /etc/os-release":
PRETTY_NAME="Debian GNU/Linux 10 (buster)" NAME="Debian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"

When I tried to execute sudo ./scripts/build-server.sh with parameter "r4.0.7" or "r4.0.9" I got the error:
~/docker-debian-testing-mongodb-stable$ sudo ./scripts/build-server.sh r4.0.7

Works like command, use a tag: sudo ./scripts/build-server.sh r4.0.9

Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'mongoose' for glob 'mongo*'
Note, selecting 'mongodb' for glob 'mongo*'
Note, selecting 'mongodb-server-core' for glob 'mongo*'
Note, selecting 'mongo-tools' for glob 'mongo*'
Note, selecting 'mongodb-server' for glob 'mongo*'
Note, selecting 'mongodb-dev' for glob 'mongo*'
Note, selecting 'mongodb-clients' for glob 'mongo*'
Package 'mongodb-dev' is not installed, so not removed
Package 'mongo-tools' is not installed, so not removed
Package 'mongodb' is not installed, so not removed
Package 'mongodb-clients' is not installed, so not removed
Package 'mongodb-server' is not installed, so not removed
Package 'mongodb-server-core' is not installed, so not removed
Package 'mongoose' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
libboost-filesystem-dev is already the newest version (1.67.0.1).
libboost-program-options-dev is already the newest version (1.67.0.1).
libboost-system-dev is already the newest version (1.67.0.1).
libboost-thread-dev is already the newest version (1.67.0.1).
build-essential is already the newest version (12.6).
libcurl4-openssl-dev is already the newest version (7.64.0-2).
gcc is already the newest version (4:8.3.0-1).
git is already the newest version (1:2.20.1-2).
glibc-source is already the newest version (2.28-10).
libffi-dev is already the newest version (3.2.1-9).
libssl-dev is already the newest version (1.1.1b-2).
python is already the newest version (2.7.16-1).
python-dev is already the newest version (2.7.16-1).
python-pip is already the newest version (18.1-5).
scons is already the newest version (3.0.1-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Requirement already up-to-date: pip in /usr/local/lib/python2.7/dist-packages (19.1)
Requirement already up-to-date: pyyaml in /usr/local/lib/python2.7/dist-packages (5.1)
Requirement already up-to-date: typing in /usr/local/lib/python2.7/dist-packages (3.6.6)
/home/trim/AutomationScripts/docker-debian-testing-mongodb-stable/build /home/trim/AutomationScripts/docker-debian-testing-mongodb-stable
Cloning into 'mongo'...
remote: Enumerating objects: 95, done.
remote: Counting objects: 100% (95/95), done.
remote: Compressing objects: 100% (79/79), done.
remote: Total 714804 (delta 22), reused 35 (delta 16), pack-reused 714709
Receiving objects: 100% (714804/714804), 457.36 MiB | 4.45 MiB/s, done.
Resolving deltas: 100% (534190/534190), done.
Checking out files: 100% (22741/22741), done.
/home/trim/AutomationScripts/docker-debian-testing-mongodb-stable/build/mongo /home/trim/AutomationScripts/docker-debian-testing-mongodb-stable/build /home/trim/AutomationScripts/docker-debian-testing-mongodb-stable
Checking out files: 100% (24893/24893), done.
Note: checking out 'tags/r4.0.7'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b

HEAD is now at 1b82c812a9 SERVER-40094 Do not prematurely reject resume attempt in DSShardCheckResumability
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Requirement already satisfied: cryptography in /usr/lib/python2.7/dist-packages (2.6.1)
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
ERROR: Could not open requirements file: [Errno 2] No such file or directory: 'etc/pip/dev-requirements.txt'

what's gone wrong? can you help me?

Hello,

Very good job!
On the other hand, I encountered a problem with PyYAML.
To overcome this problem, I put in build-server.sh:

pip install -U pip typing #pyyaml
and

install the python requirements

#pip install -r etc/pip/dev-requirements.txt
pip install --ignore-installed PyYAML
pip install -r buildscripts/requirements.txt

Thanks.

Ne0Lux-C1Ph3r

Hey, thank you for your script, i'm running into trouble, full error log here:

https://pastebin.com/YhyiVba6

Debian 10 Buster 4.19.0-5-amd64

Python 3.73 default, also python 2.7 installed, pip and pip3 should be up to date.

"typing" is in pip/pip3 installed.

I'm clueless what the error is all about, could you take a look?

Thanks in advance.

Cheers Timmy