On Mon, 4 Jun 2018, Riccardo Mottola via macports-users wrote: > coulkd this be due to the latest C++ fixes of macports? Fixed in 2.5.1, I'm told, hence my query as to whether it's a known issue before I waste time filing a duplicate bug report. -- Dave