On 2018-11-12, Michael Steeves <stee...@raingods.net> wrote: > I've updated my system to the latest snapshot, and then upgraded all the > packages (and rebooted for good measure), but I still see these errors. I > assume there's no simple fix for this, and I'd need to either file bugs (and > wait until they're fixed), or else build the ports myself?
The problem is known and understood. It's now a matter of either (1) pushing for a general solution in base or (2) fixing all 30+ potentially affected ports individually. We'll just have to wait until somebody gets around to doing either. Building the port yourself will just reproduce the problem. -- Christian "naddy" Weisgerber na...@mips.inka.de
