I've tried to track down these issues (unfortunatly I only have an amd64 testsystem right now):
## i386 It seems the issue was in typenum and also showed up in librsvg in debian[1], where it was fixed by cherry-picking a patch[2] from upstream. This commit was part of the typenum 1.11.0 release, so this issue should be resolved by bumping this port. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926840 [2]: https://github.com/paholg/typenum/commit/14a3322d1081fd63d5eb44bf8ab8f90676208228 ## sparc64 This one is more difficult, it includes the info which crate is actually failing (which is super useful), but the error message is very generic and I'm having trouble pin-pointing this bug without a sparc64 system or a backtrace with RUST_BACKTRACE=1 set. The ring dependency was updated from 0.14.6 to 0.16.7, so there's a chance this was resolved upstream. > First, a general remark: I strongly want that such Rust port to have a > maintainer. Else, it means I will have to do it, and I have no time for > such port that only work on few platforms, and where nobody care if it > breaks. Currently, it is marked BROKEN on i386 and sparc64. Both of these problems are most likely resolved with this port update (and the patch that bumps libc), I don't have a good way to test this though besides removing both BROKEN lines and checking if the build passes. Ideas very welcome. I'm happy to look into issues when somebody pings me. There's probably some overlap anyway since I'm both the upstream and also one of the debian rust maintainers, but I should also point out that I'm still very new to the openbsd ports system (and I had to look up how to generate a diff with cvs when I sent this patch). If that's sufficient to become the maintainer I would be happy to do so. Thanks!
