On 01/11/2025 23:10, Jeremy Drake via Cygwin-apps wrote:
As far as a published-on-the-mirrors test package, it would need some
packaging love first, filling in the metadata properly, and probably being
split into multiple packages.
I've given this a home at https://cygwin.com/cgit/cygwin-packages/rust/
I polished the build a bit and split it up into subpackages.
I'm inclined to deploy as is, since it's unlikely to get any better any
time soon, and is potentially useful as is.
Things that still need looking into:
* are any of the test failures significant?
* The rust stdlib as a shared library is installed to a private
directory. This probably doesn't work without rpath, but being a rust
ignoramus I can't work out how to build something that wants to use it
to test that assumption. (Upstream issue saying everything is fine [1]).
[1] https://github.com/rust-lang/rust/issues/149050
* debuginfo is disabled (in bootstrap.toml). Maybe we can turn this on
for the stage 2 build? Or maybe that's more likely to cause fork
failures since we run the unstripped executables?
* rust-analyzer and the documentation aren't built (due to fork failures)
(Presumably both of these issues are improved by the posix_spawn
implementation which avoids fork/exec if possible, but maybe there's
something else going on here: is it what we do, or the size of the LLVM
library which is causing extra problems?)
Jeremy,
Thanks very much for your work on this!
