[Buildroot] Unable to compile current master

[Mark Jackson]

On 04/07/17 12:45, Arnout Vandecappelle wrote:
> 
> 
> On 04-07-17 12:37, Mark Jackson wrote:
>> On 03/07/17 16:57, Arnout Vandecappelle wrote:
>>>
>>>
>>> On 03-07-17 17:14, Mark Jackson wrote:
>>>> I'm trying to bring an old 2012 buildroot project up-to-date, so to test my current setup I've branched the git master and tried:-
>>>>
>>>> $ git checkout origin/master -b master
>>>> $ git reset --hard origin/master
>>>> $ make clean
>>>> $ make beaglebone_defconfig
>>>> $ make
>>>>
>>>> But this fails when compiling gcc with the following:-
>>>>
>>>> ...
>>>> /usr/bin/g++ -fno-PIE -c   -O2 -I/home/mpfj/buildroot/output/host/usr/include -DIN_GCC  -DCROSS_DIRECTORY_STRUCTURE   -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings   -DHAVE_CONFIG_H -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/../include -I../../gcc/../libcpp/include -I/home/mpfj/buildroot/output/host/usr/include -I/home/mpfj/buildroot/output/host/usr/include -I/home/mpfj/buildroot/output/host/usr/include  -I../../gcc/../libdecnumber -I../../gcc/../libdecnumber/dpd -I../libdecnumber -I../../gcc/../libbacktrace   -o insn-extract.o -MT insn-extract.o -MMD -MP -MF ./.deps/insn-extract.TPo insn-extract.c
>>>> Makefile:2201: recipe for target 's-attrtab' failed
>>>
>>>    Apparently genattrtab failed but I can't find any output.
>>>
>>>    Can you continue the build with BR2_JLEVEL=1 ? That should make any error
>>> message easier to locate.
>>>
>>
>> Okay ... with JLEVEL=1 (rather than 0 (auto)), it compiles !!
>>
>> So it must be some strange parallel compilation bug ...
> 
>   Actually it's more likely that your system ran out of memory. GCC uses some
> weird internal memory allocator that will fail invisibly in some situations
> (i.e. without invoking OOM killer or anything obvious like that).
> 
>   Those generators were apparently running all in parallel in your build, so that
> could indeed explain memory exhaustion.
> 
>   Regards,
>   Arnout
> 

Confirmed ... I've upped my VM from 2GB to 8GB and it all now compiles with JLEVEL=0 (auto).

FYI memory usage peaked at about 2.5GB.

Cheers
Mark J.