Created attachment 210064 [details]
full build log
I think that the revelent part of the log is here:
--- knsec3hash ---
/usr/local/lib/libidn2.so.0:(.text+0x22a0): multiple definition of `_idn2_punycode_encode@IDN2_0.0.0'
/usr/local/lib/libidn2.so.0:(.text+0x2680): multiple definition of `_idn2_punycode_decode@IDN2_0.0.0'
cc: error: linker command failed with exit code 1 (use -v to see invocation)
*** [knsec3hash] Error code 1
However, I didn’t enabled IDN and it’s disabled by default, the full log is attached.
Alarig Le Lay
Seems it is this in libidn2:
CC'd libidn2 maintainer.
I became aware of the problem.
It is / will be solved in PR 242665
Created attachment 210074 [details]
Knot DNS 2.9.2
Since it's usual to have one commit per PR;
maybe let's first apply this patch - which will solve this problem,
instead of trying to solve everything at once.
The port built this night :)
Still every single mutation in my patch is an improvement.
I'd prefer to have it committed ahead of closing PR 242665, which still should solve the long ongoing i386 atomic issue.
This PR can be closed.
It's addressed in PR 242665 (in case it still was a problem).
The mentioned problem caused by libidn2 was fixed in r520636.