You can say i did it completely wrong, but after some partial upgrades, i decided to test "emerge system", and added USE="vanilla", without much thinking (it turned out this flag accepted not only by gcc, binutils, libtool - but also by bash, coreutils ...). After some 18h of compiling emerge bail out with error. Ld segfaulted in compiler test in opcodes subdir. I have logs and will post them as attachments. But not sure if building (re-building, in my case) system with USE=vanilla is supported in any way, especially if mixed with ccache ? People with faster mips hardware can test, if their system can build vanilla binutils package, and if this package fully-functional .... ? Reproducible: Didn't try Steps to Reproduce: 1. Try to USE="vanilla" emerge system (not 'emerge -e system') Actual Results: It will fail, probably, at binutils compilation. Expected Results: Bail out, if building unpatched toolchain component(s) aren't supported on this platform.
Created attachment 250315 [details] build log
Created attachment 250317 [details] environment file
Created attachment 250319 [details] eclass-debug log
Created attachment 250321 [details] elibtool
Created attachment 250323 [details] config.log from opcodes sub-dir.
Created attachment 250325 [details] config.log from binutils's build directory, top level.
Created attachment 250333 [details] list of packages i'm currently trying to emerge As you can see, 'emerge -e system' adds few more updates (compared to just emerge system), some of them can be important for building binutils later. List was captured with 'emerge -pe system > system_list 2>&1' Note some packages were compiled with "vanilla" USE flag during failed 'emerge system' run. I'll update this bug when 1) emerge finished or 2) failed at some point
global USE=vanilla in make.conf is not supported. you should be picking this only for packages where you actually understand the consequences. sometimes we apply patches when USE=-vanilla that fix upstream problems.
