Date: Mon, 10 Feb 2020 11:56:32 +0000 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) Message-ID: <bug-233971-7788-wNUUJHSyVF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233971-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-233971-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=3D233971 Sean Champ <lab+bsd@thinkum.space> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |Closed Resolution|--- |FIXED --- Comment #3 from Sean Champ <lab+bsd@thinkum.space> --- 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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-233971-7788-wNUUJHSyVF>