The ports tree is still susceptible to fallout from the migration to
clang(1), but I don't see any mention on the
ports@ mailing list on recently identified problems regarding this port.
Before suggesting that you post to
ports@ yourself, are you sure that the ports tree was updated at the same time as the base system last Thursday, given that you recompiled
audio/ncmpcpp with debug information? If you do ultimately talk to the developers, they will ask the same question.