I recently saw a similar problem and thought I had looked into something, but this was it. https://lists.freebsd.org/archives/freebsd-ports/2024-February/005546.html
David Wolfskill wrote on 2024/03/05 10:27: > albert(14.0-S)[14] pdf2ps pdf/bike.pdf >/tmp/bike.ps > ld-elf.so.1: /usr/local/lib/libidn.so.12: version LIBIDN_1.0 required by > /usr/local/lib/libgs.so.10 not defined > * Is there a way to prevent the problem from occurring? > > * Now that the problem has definitely occurred, is there a way to > detect that a (poudriere-built) package suffers from that problem? It seems that not only fstrm but also libidn contained the same problem. This would seem to indicate that there has been a change on the part of the OS that reverses the availability of version-script in your environment. However, since the package version has not changed, the actual package used would not have been reinstalled. And since a version-script availability was reversed at the same time as some dependent package was rebuilt, all packages created in poudriere were assumed to be so. I guess that's how it is :) For its part, configure seems to output the following line checking if LD -Wl,--version-script works... yes If you are still keeping a large amount of poudriere logs, can you check to see if there is a mix of yes and no on the lines? Regards.
