On Thu, Apr 2, 2020 at 9:27 AM Tim Rühsen <[email protected]> wrote:
>
> Hi Jeff,
>
> I believe this is not related to libidn2.
>
> ...
>
> So it looks like you need 'nm' somehow working together with your
> compiler !?

This is kind of weird... Autotools is picking the lamest nm it can
find (the Solaris one, which is more anemic then Posix):

$ find /usr -name nm
/usr/xpg4/bin/nm
/usr/gnu/i386-pc-solaris2.11/bin/nm
/usr/gnu/bin/nm
/usr/bin/nm

I must have screwed my path up.

libidn2-2.3.0 is probably OK.

Thanks.

Jeff

Reply via email to