Date: Sat, 02 Dec 2017 07:48:49 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 221029] AMD Ryzen: strange compilation failures using poudriere or plain buildkernel/buildworld Message-ID: <bug-221029-8-WF3dX9EjBt@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221029-8@https.bugs.freebsd.org/bugzilla/> References: <bug-221029-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029 --- Comment #105 from Mark Millard <markmi@dsl-only.net> --- (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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221029-8-WF3dX9EjBt>