From owner-freebsd-bugs@freebsd.org Sat Dec 2 07:48:49 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35321DF6E9B for ; Sat, 2 Dec 2017 07:48:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2300D6537B for ; Sat, 2 Dec 2017 07:48:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vB27mmZL023835 for ; Sat, 2 Dec 2017 07:48:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 221029] AMD Ryzen: strange compilation failures using poudriere or plain buildkernel/buildworld Date: Sat, 02 Dec 2017 07:48:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2017 07:48:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029 --- Comment #105 from Mark Millard --- (In reply to Mark Millard from comment #104) FYI: So far what failed initially but built in a later retry of a bulk -a (no -C ) is: tome4-1.5.5 sv-gimp-help-html-2.8.2 zh_CN-gimp-help-html-2.8.2 reflex-20170521 tfel-mfront-2.0.4_1 p5-B-C-1.55 mpqc-mpich-2.3.1_30 samba45-4.5.14 iroffer-dinoex-3.30_2 nifticlib-2.0.0_1 apache-openoffice-devel-4.2.1810071_1,4 en_GB-gimp-help-html-2.8.2 de-gimp-help-html-2.8.2 ca-gimp-help-html-2.8.2 go-1.9.2,1 This is after a couple of retry attempts that could add to the list. There are some examples where looking at the logs and the detailed build order leads me to expect that ALLOW_MAKE_JOBS=3Dyes might not be supported correctly. An example is: tfel-mfront-2.0.4_1 : /usr/bin/ld: cannot find -lMFrontLogStream c++: error: linker command failed with exit code 1 (use -v to see invocatio= n) *** [mfront] Error code 1 which may have just happened before libMFrontLogStream was available. There were a couple of cases of the initial failures being: Killing runaway build after 7200 seconds with no output but the retry did not get that. (Different competing processes were involved.) None of that list were SIGSEGV or SIGBUS failures according to the log files. The sequence is: QUEUE BUILT FAIL SKIP IGNORE REMAIN 27777 25049 364 2015 349 0 2730 185 354 1840 351 0 2547 266 348 1580 353 0 Things that moved from SKIP to BUILT were generally because of depending on something that I turned off WITH_DEBUG=3D for as I went along (such as www/*webkit* instead of www/qt5-webkit* ). It does appear that the 1950X threadripper avoids the issues that I saw with the 1800X. --=20 You are receiving this mail because: You are the assignee for the bug.=