On Mon, Sep 20, 2021 at 10:15:08AM +0100, Stuart Henderson wrote:
> On 2021/09/19 22:01, k...@openbsd.org wrote:
> > http://build-failures.rhaalovely.net/sparc64/2021-09-18/devel/libidn2.log

> It's the usual one again with duplicate symbols.

> Comparing files from the libunistring and libiconv packages from
> two builds, one having the problem one not, the only files with any
> difference are the static libraries, and after sed'ing them to
> replace timestamps of the .o files there is no remaining difference,
> so the issue seem to be in the libidn2 build rather than one of the
> ports it depends on.

> If the build machines are not yet cleaned, can you try

> (0. save a copy of the libidn2 build dir first)

Unfortunately the directory is basically empty. I had wiped to try a fix
by swapping compilers. Which failed even more weirdly and had an essentially
empty build directory.

> 1. cleaning libidn2 and attempt a rebuild as-is, is there any change?

I removed my crude fix attempt, restarted the build and the rebuild just
worked this time. *sigh*


--Kurt

Reply via email to