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 wrote:
>Hi Arthur
>
>On Tue, Aug 14, 2018 at 08:3
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
Package: gcc-8
Version: 8.2.0-3
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Building a kernel using
CONCURRENCY_LEVEL=2 \
MAKEFLAGS="HOSTCC=gcc-8 CC=gcc-8 LD=ld.gold V=1 VERBOSE=1 KCFLAGS=-m
3 matches
Mail list logo
