I switched to clang-3.7, and ran into the same problem
[1484/2025] Building CXX object
tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o
FAILED: /usr/bin/clang++-3.7 -DCLANG_ENABLE_ARCMT
-DCLANG_ENABLE_OBJC_REWRITER -DCLANG_ENABLE_STATIC_ANALYZER
-DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-stack-protector -fPIC
-fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings
-Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long
-Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor
-std=c++11 -fcolor-diagnostics -ffunction-sections -fdata-sections
-fno-common -Woverloaded-virtual -Wno-nested-anon-types -O3
-Itools/clang/lib/ASTMatchers/Dynamic
-I/home/buckley/swift/llvm/tools/clang/lib/ASTMatchers/Dynamic
-I/home/buckley/swift/llvm/tools/clang/include -Itools/clang/include
-Iinclude -I/home/buckley/swift/llvm/include -UNDEBUG -fno-exceptions
-fno-rtti -MMD -MT
tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o
-MF
tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o.d
-o
tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o
-c /home/buckley/swift/llvm/tools/clang/lib/ASTMatchers/Dynamic/Registry.cpp
clang: error: unable to execute command: Killed
clang: error: clang frontend command failed due to signal (use -v to see
invocation)
Ubuntu clang version 3.7.0-2ubuntu4 (tags/RELEASE_370/final) (based on LLVM
3.7.0)
Target: x86_64-pc-linux-gnu
Thread model: posix
clang: note: diagnostic msg: PLEASE submit a bug report to http://bugs.debian.org/ and include the crash backtrace, preprocessed
source, and associated run script.
clang: note: diagnostic msg:
···
********************
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang: note: diagnostic msg: /tmp/Registry-f30d0f.cpp
clang: note: diagnostic msg: /tmp/Registry-f30d0f.sh
clang: note: diagnostic msg:
********************
[1484/2025] Building CXX object
tools/clang/lib/ASTMatchers/CMakeFiles/clangASTMatchers.dir/ASTMatchFinder.cpp.o
ninja: build stopped: subcommand failed.
./swift/utils/build-script: command terminated with a non-zero exit status
1, aborting
On Wed, Mar 2, 2016 at 12:42 PM, Dmitri Gribenko <gribozavr@gmail.com> wrote:
On Wed, Mar 2, 2016 at 12:25 PM, Michael Buckley > <michael@buckleyisms.com> wrote:
> Thanks. Apt-get reports that my clang is up to date (Ubuntu clang version
> 3.6.2-1), but I'm happy to wait for a newer version. I was just
attempting
> to compile it to make sure a change I made worked on Linux, but it's not
> urgent.
There's clang-3.7 in the repo, could you try that?
Thank you for checking! It could be a different problem. For
example, how many cores, and how much memory and swap does your
machine have?
Dmitri
···
On Wed, Mar 2, 2016 at 1:47 PM, Michael Buckley <michael@buckleyisms.com> wrote:
I switched to clang-3.7, and ran into the same problem
[1484/2025] Building CXX object
tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o
FAILED: /usr/bin/clang++-3.7 -DCLANG_ENABLE_ARCMT
-DCLANG_ENABLE_OBJC_REWRITER -DCLANG_ENABLE_STATIC_ANALYZER
-DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-stack-protector -fPIC
-fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings
-Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long
-Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor
-std=c++11 -fcolor-diagnostics -ffunction-sections -fdata-sections
-fno-common -Woverloaded-virtual -Wno-nested-anon-types -O3
-Itools/clang/lib/ASTMatchers/Dynamic
-I/home/buckley/swift/llvm/tools/clang/lib/ASTMatchers/Dynamic
-I/home/buckley/swift/llvm/tools/clang/include -Itools/clang/include
-Iinclude -I/home/buckley/swift/llvm/include -UNDEBUG -fno-exceptions
-fno-rtti -MMD -MT
tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o
-MF
tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o.d
-o
tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o
-c /home/buckley/swift/llvm/tools/clang/lib/ASTMatchers/Dynamic/Registry.cpp
clang: error: unable to execute command: Killed
clang: error: clang frontend command failed due to signal (use -v to see
invocation)
Ubuntu clang version 3.7.0-2ubuntu4 (tags/RELEASE_370/final) (based on LLVM
3.7.0)
Target: x86_64-pc-linux-gnu
Thread model: posix
clang: note: diagnostic msg: PLEASE submit a bug report to http://bugs.debian.org/ and include the crash backtrace, preprocessed
source, and associated run script.
clang: note: diagnostic msg:
********************
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang: note: diagnostic msg: /tmp/Registry-f30d0f.cpp
clang: note: diagnostic msg: /tmp/Registry-f30d0f.sh
clang: note: diagnostic msg:
********************
[1484/2025] Building CXX object
tools/clang/lib/ASTMatchers/CMakeFiles/clangASTMatchers.dir/ASTMatchFinder.cpp.o
ninja: build stopped: subcommand failed.
./swift/utils/build-script: command terminated with a non-zero exit status
1, aborting
On Wed, Mar 2, 2016 at 12:42 PM, Dmitri Gribenko <gribozavr@gmail.com> > wrote:
On Wed, Mar 2, 2016 at 12:25 PM, Michael Buckley >> <michael@buckleyisms.com> wrote:
> Thanks. Apt-get reports that my clang is up to date (Ubuntu clang
> version
> 3.6.2-1), but I'm happy to wait for a newer version. I was just
> attempting
> to compile it to make sure a change I made worked on Linux, but it's not
> urgent.
There's clang-3.7 in the repo, could you try that?
So I'm not running on real hardware. but in VM. I allowed VMWare Fusion
(version 7.1.1) to set the defaults for creating a new Ubuntu image. Here's
what the VM is currently set to.
RAM: 1 GB (The host system has 16 GB total, so I could allocate more)
Processors: 4 cores: The host system has 8 cores). However, I also tried
running the VM with only 1 core, and ran into the same issue.
Disk Image: 20 GB total, 9.5 GB Free. (The host system has a 1 TB drive,
but it's partitioned to boot multiple versions of OS X and Windows, each
with full development environments, to 20 GB was really all I could spare.)
Swap: VMWare seems to have created a 1.1 GB Swap partition (in addition to
the 20 GB disk), and a 1.1 GB extended partition)
···
On Wed, Mar 2, 2016 at 1:49 PM, Dmitri Gribenko <gribozavr@gmail.com> wrote:
Thank you for checking! It could be a different problem. For
example, how many cores, and how much memory and swap does your
machine have?
Dmitri
On Wed, Mar 2, 2016 at 1:47 PM, Michael Buckley <michael@buckleyisms.com> > wrote:
> I switched to clang-3.7, and ran into the same problem
>
> [1484/2025] Building CXX object
>
tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o
> FAILED: /usr/bin/clang++-3.7 -DCLANG_ENABLE_ARCMT
> -DCLANG_ENABLE_OBJC_REWRITER -DCLANG_ENABLE_STATIC_ANALYZER
> -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS
> -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-stack-protector -fPIC
> -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter
-Wwrite-strings
> -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long
> -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor
> -std=c++11 -fcolor-diagnostics -ffunction-sections -fdata-sections
> -fno-common -Woverloaded-virtual -Wno-nested-anon-types -O3
> -Itools/clang/lib/ASTMatchers/Dynamic
> -I/home/buckley/swift/llvm/tools/clang/lib/ASTMatchers/Dynamic
> -I/home/buckley/swift/llvm/tools/clang/include -Itools/clang/include
> -Iinclude -I/home/buckley/swift/llvm/include -UNDEBUG -fno-exceptions
> -fno-rtti -MMD -MT
>
tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o
> -MF
>
tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o.d
> -o
>
tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o
> -c
/home/buckley/swift/llvm/tools/clang/lib/ASTMatchers/Dynamic/Registry.cpp
> clang: error: unable to execute command: Killed
> clang: error: clang frontend command failed due to signal (use -v to see
> invocation)
> Ubuntu clang version 3.7.0-2ubuntu4 (tags/RELEASE_370/final) (based on
LLVM
> 3.7.0)
> Target: x86_64-pc-linux-gnu
> Thread model: posix
> clang: note: diagnostic msg: PLEASE submit a bug report to
> http://bugs.debian.org/ and include the crash backtrace, preprocessed
> source, and associated run script.
> clang: note: diagnostic msg:
> ********************
>
> PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
> Preprocessed source(s) and associated run script(s) are located at:
> clang: note: diagnostic msg: /tmp/Registry-f30d0f.cpp
> clang: note: diagnostic msg: /tmp/Registry-f30d0f.sh
> clang: note: diagnostic msg:
>
> ********************
> [1484/2025] Building CXX object
>
tools/clang/lib/ASTMatchers/CMakeFiles/clangASTMatchers.dir/ASTMatchFinder.cpp.o
> ninja: build stopped: subcommand failed.
> ./swift/utils/build-script: command terminated with a non-zero exit
status
> 1, aborting
>
>
> On Wed, Mar 2, 2016 at 12:42 PM, Dmitri Gribenko <gribozavr@gmail.com> > > wrote:
>>
>> On Wed, Mar 2, 2016 at 12:25 PM, Michael Buckley > >> <michael@buckleyisms.com> wrote:
>> > Thanks. Apt-get reports that my clang is up to date (Ubuntu clang
>> > version
>> > 3.6.2-1), but I'm happy to wait for a newer version. I was just
>> > attempting
>> > to compile it to make sure a change I made worked on Linux, but it's
not
>> > urgent.
>>
>> There's clang-3.7 in the repo, could you try that?
>>
>> Dmitri
>>
>> --
>> main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
>> (j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr@gmail.com>*/
>
>
You need at least 10 GB of RAM + swap in total to successfully finish
the compilation. More if you are building with debug info. Even more
if you have many cores.
Dmitri
···
On Wed, Mar 2, 2016 at 2:48 PM, Michael Buckley <michael@buckleyisms.com> wrote:
So I'm not running on real hardware. but in VM. I allowed VMWare Fusion
(version 7.1.1) to set the defaults for creating a new Ubuntu image. Here's
what the VM is currently set to.
RAM: 1 GB (The host system has 16 GB total, so I could allocate more)
That's very good to know, thanks. I'll try cranking up the RAM allocation
to my VM when I don't need to use my machine for a while and give it a shot
then.
···
On Wed, Mar 2, 2016 at 2:52 PM, Dmitri Gribenko <gribozavr@gmail.com> wrote:
On Wed, Mar 2, 2016 at 2:48 PM, Michael Buckley <michael@buckleyisms.com> > wrote:
> So I'm not running on real hardware. but in VM. I allowed VMWare Fusion
> (version 7.1.1) to set the defaults for creating a new Ubuntu image.
Here's
> what the VM is currently set to.
>
> RAM: 1 GB (The host system has 16 GB total, so I could allocate more)
You need at least 10 GB of RAM + swap in total to successfully finish
the compilation. More if you are building with debug info. Even more
if you have many cores.