Simon Josefsson <si...@josefsson.org> writes: > I think that it would be better for nettle to maintain separate > build-images and not rely on other project's build-images. We could add > 'gnutls/nettle-build-images' for this if you want? Or is there some > other more canonical home for nettle on gitlab already?
This is now setup, at https://git.lysator.liu.se/nettle/build-images, mirrored to https://gitlab.com/gnutls/nettle-build-images, and resulting images published at https://gitlab.com/gnutls/nettle-build-images/container_registry/5633274 Thanks to Simon and Daiki for help setting this up. Currently one with tools for native builds (including the gnutls build), one qiwth cross compilers and qemu for cross builds (with cross-compilers and qemu), and one with clang tools, for it's static analyzer. Maybe the gnutls build should use its own image, or reuse something from gnutls/build-images, since it has lots of additional dependencies. I'm migrating nettle's CI setup on this branch, https://gitlab.com/gnutls/nettle/-/tree/ci-nettle-build-images?ref_type=heads, which is now partly working, both for native and cross builds. New failures: One report from the static analyzer, that appear valid (but harmless). Test failures of poly1305 on powerpc64el, which I haven't been able to reproduce in a local cross build + qemu. (poly1305 happens to be the only ppc assembly depending om power9 features). Regards, /Niels -- Niels Möller. PGP key CB4962D070D77D7FCB8BA36271D8F1FF368C6677. Internet email is subject to wholesale government surveillance. _______________________________________________ nettle-bugs mailing list -- nettle-bugs@lists.lysator.liu.se To unsubscribe send an email to nettle-bugs-le...@lists.lysator.liu.se
