Date: Mon, 12 Oct 2020 19:23:46 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 246700] [exp-run] Update GCC_DEFAULT from 9 to 10 Message-ID: <bug-246700-7788-6Ic7GYDqRw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-246700-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-246700-7788@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=3D246700 --- Comment #67 from Mark Linimon <linimon@FreeBSD.org> --- Here is the list that I show that have not been updated (at least per this = PR). This is a small enough list that IMHO we could easily just commit, and perh= aps either restrict the GCC version in them or mark them BROKEN. But I would like to request one more exp-run before I take that action. R-cran-mvtnorm-0.9.96_20.log beatslash-lv2-1.0.6_1.log drumgizmo-0.9.18.1.log electricsheep-2.7_6,1.log gotoblas-2.1.13.3.4.0_16.log guitarix-lv2-0.40.0.log hdf-4.2.11_8,1.log libinstpatch-1.1.5.log meek-0.35.0.log mlton-20100608_8.log molden-5.8.2_3,1.log mumps4-4.10.0_3.log ncbi-blast+-2.10.0_1.log ncbi-cxx-toolkit-21.0.0_2.log openmpi-4.0.3.log openmpi3-3.1.6.log openmsx-0.15.0_2.log py27-biopython-1.77.log py37-open3d-python-0.2_4.log rocksdb-lite-6.10.1_1.log srain-1.1.0.log tamgamp-lv2-g20200514.log tigcc-0.96.b8_10.log valgrind-3.10.1.20160113_8,1.log valgrind-devel-3.10.1.20160113_7,1.log waybar-0.9.2_1.log wsjtx-2.1.2_1.log xlapack-3.5.0_6.log xorp-1.8.5_14.log --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246700-7788-6Ic7GYDqRw>