Apparently already known and a proposed fix had been submitted in PR #588, but there was no github issue opened for it (and thus for me at least it wasn't evident that it was a known bug).
I encountered while building an open-source project and I could provide assistance with reproducing if that would help.
In my build conditions, the patch in #588 solves the issue, but that is of course no guarantee for other environments.
Apparently already known and a proposed fix had been submitted in PR #588, but there was no github issue opened for it (and thus for me at least it wasn't evident that it was a known bug).
I encountered while building an open-source project and I could provide assistance with reproducing if that would help.
In my build conditions, the patch in #588 solves the issue, but that is of course no guarantee for other environments.