Replying to metbic:
Does it have to do with the thread about libidn2?
#63309
Nothing whatsoever.
Replying to evanmiller:
This issue looks similar: https://legacy.imagemagick.org/discourse-server/viewtopic.php?t=28136
Apparently there is supposed to be a global_symbol_pipe variable that is defined during configure, but that's not happening for some reason. This is a good explanation, though it lacks a solution:
https://lists.gnu.org/archive/html/bug-libtool/2015-07/msg00000.html
That bug-libtool post says "it only occurs due to outside influences". If that's so, maybe building with trace mode would hide those outside influences from the build.
sudo port clean libidn
sudo port -t upgrade libidn
Replying to metbic:
it's already too late ... the older version is no longer there
port installed libidn
The following ports are currently installed:
libidn @1.36_0+universal (active)
If the older version is no longer installed then indeed you cannot follow the steps in the first section of that wiki page, "Reactivating an older version that's still installed", but you can follow the steps in the subsequent section, "(Re)installing an older version that's no longer installed". However, reinstalling older versions of ports is not the intended solution for issues; we should try to figure out what is wrong and fix it with the current versions.
However, you've shown above that you have libidn 1.36 installed, which is not the current version; the current version is 1.38. The updates to 1.37 and then 1.38 were made in 2021.
