When compiling webkit-gtk-2.4.4 emerge fails on emake as follows: ./Source/WTF/wtf/Vector.h:374:5: internal compiler error: Segmentation fault build.log attached. Reproducible: Always Steps to Reproduce: MAKEOPTS="--jobs=1" emerge --update -1 =net-libs/webkit-gtk-2.4.4:3/25 Actual Results: libtool: compile: x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -DBUILDING_WebCore -DBUILDING_WEBKIT -Wall -W -Wcast In file included from ./Source/JavaScriptCore/heap/GCIncomingRefCounted.h:30:0, from ./Source/JavaScriptCore/runtime/ArrayBuffer.h:29, from ./Source/JavaScriptCore/heap/Heap.h:25, from ./Source/JavaScriptCore/runtime/WriteBarrier.h:31, from ./Source/JavaScriptCore/runtime/PropertyStorage.h:29, from ./Source/JavaScriptCore/runtime/IndexingHeader.h:29, from ./Source/JavaScriptCore/runtime/ArrayConventions.h:24, from ./Source/JavaScriptCore/runtime/JSArray.h:24, from ./Source/JavaScriptCore/bytecode/ArrayAllocationProfile.h:30, from ./Source/JavaScriptCore/runtime/JSGlobalObject.h:25, from ./Source/WebCore/bindings/js/JSDOMGlobalObject.h:31, from ./Source/WebCore/bindings/js/JSDOMBinding.h:27, from DerivedSources/WebCore/JSSVGFilterElement.h:26, from DerivedSources/WebCore/JSSVGFilterElement.cpp:25: ./Source/WTF/wtf/Vector.h: In instantiation of 'void WTF::VectorBuffer<T, 0ul>::swap(WTF::VectorBuffer<T, 0ul>&) [w ./Source/WTF/wtf/Vector.h:679:9: required from 'void WTF::Vector<T, inlineCapacity, OverflowHandler>::swap(WTF::V ./Source/WTF/wtf/Vector.h:786:5: required from 'WTF::Vector<T, inlineCapacity, OverflowHandler>::Vector(WTF::Vect ./Source/WebCore/svg/SVGLengthList.h:30:7: required from here ./Source/WTF/wtf/Vector.h:374:5: internal compiler error: Segmentation fault
Created attachment 383520 [details] build.log.gz
Created attachment 383522 [details] emerge --info
Do you have enough memory? Could you look for any errors in dmesg output when getting the failure? Are you getting the same exact failure on each run?
Thank you Pacho for taking the time to look at this. It turns out it was indeed due to a full disk (I have tmpfs with 2GB), but I didn't recognise this as I generally get a message indicating a full device. In this case, as you can see from the error log there was no such indication. Closing.