From owner-freebsd-ports-bugs@freebsd.org Mon Feb 10 11:56:33 2020 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1FE8523792F for ; Mon, 10 Feb 2020 11:56:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 48GPWj05gGz4N4t for ; Mon, 10 Feb 2020 11:56:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 017AD23792E; Mon, 10 Feb 2020 11:56:33 +0000 (UTC) Delivered-To: ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0140123792D for ; Mon, 10 Feb 2020 11:56:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48GPWh6JRfz4N4s for ; Mon, 10 Feb 2020 11:56:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id CF4C31EB9A for ; Mon, 10 Feb 2020 11:56:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 01ABuWSi039971 for ; Mon, 10 Feb 2020 11:56:32 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 01ABuW4o039970 for ports-bugs@FreeBSD.org; Mon, 10 Feb 2020 11:56:32 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 233971] emuators/virtualbox-ose 5.2.22 fails to link on FreeBSD 11.2 (ld: error: unknown argument: --no-check-sections) Date: Mon, 10 Feb 2020 11:56:32 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: lab+bsd@thinkum.space X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: merge-quarterly? X-Bugzilla-Changed-Fields: bug_status resolution 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-ports-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2020 11:56:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233971 Sean Champ changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |Closed Resolution|--- |FIXED --- Comment #3 from Sean Champ --- FreeBSD 11.2 was marked as deprecated, at some point. With the assistance o= f a thumb drive, I've updated to FreeBSD 12.1 subsequently. I've not seen any b= uild failure for VirtualBox, since then. This, I presume, is a closed bug now. If any exposition may serve a whatsoever informative, albeit post hoc: My own build configuration may have introduced some quirks into the compiler tooclhain, from the base system build. Though I'm afraid I've not stored any exact log of the toolchain configuration I was using, at that time, it may = have been after I'd stopped building binutils in the base system. I'm not certain how that may have affected the resulting toolchain, as I had not ever uninstalled the original binutils binaries, from whenever was the last time that I'd built binutils under the base system (November 2018? for GNU as, on one machine).=20 After noticing some of the work about binutils under the FreeBSD master bra= nch, looking forward to any subsequent updates there - will try to cherry-pick s= ome of those changes to a local patch branch on releng/12.1, for purpose of testing. Furthermore, I'd been setting CPUTYPE in the build - using core2 such that = I'd believed might have represented a common subset of functionality for the two machines that the builds were being used on. In retrospect, I'm not sure how well that may have actually worked out. It had not appeared locally, as an obvious concern, until trying to run the base system build under an earlier= CPU architecture - with a core i7 CPU, namely. Possibly, it may have affected anything, in any quirky but less obvious way, up to this time.=20 One of the machines is apparently using an ivybridge CPU, while the other h= as a broadwell CPU, beside this newer (older) i7 machine. Regardless, I'll try to manage my own CPUTYPE-specific builds more selectively, now, with some more hacks on the local make.conf. I'm certain it's a closed bug, by now - have been able to build virtualbox = with clang 8.0.1 from the base system, using releng/12.1 src, even under what ma= y be something of a badly hacked toolchain build. --=20 You are receiving this mail because: You are the assignee for the bug.=