Hi, it appears that the symptoms were caused by running the build under a kernel revision (between 4.18.0-rc8 and 4.18.0) that had issues.
Apologies for the trouble. Please close the bug report. On 14 August 2018 4:07:30 pm ACST, Bastian Blank <wa...@debian.org> wrote: >Hi Arthur > >On Tue, Aug 14, 2018 at 08:32:18AM +0930, Arthur Marsh wrote: >> results in machine shutdown. Setting CONCURRENCY_LEGVEL=1 avoids the >problem. > >While gcc may use the system in unusual ways, it does not have the >permissions to shutdown a system. > >If a user space program breaks a system, it is either a broken kernel >or >broken hardware. > >> -- System Information: >> Debian Release: buster/sid >> APT prefers oldstable >> APT policy: (500, 'oldstable'), (1, 'experimental') >> Architecture: i386 (i686) > >buster and oldstable? This policy makes no sense. > >> Kernel: Linux 4.18.0+ (SMP w/2 CPU cores; PREEMPT) > >I don't think we have unreleased kernels in Debian. You may want to >re-chekc this using a released version. > >Bastian > >-- >Humans do claim a great deal for that particular emotion (love). > -- Spock, "The Lights of Zetar", stardate 5725.6 -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
