Hi!

I don't have a solution for you, but I did see a similar difference when I once experimented with building WebAssembly targets along with the main rust toolchain. Something in the result seems to be including the host information, and that should probably be fixed, but I'm not sure where that is coming from.

Regarding mingw-rust, would you really want an entirely separate toolchain? Or should we see about adding mingw targets as a subpackage of the main rust.srpm? We would still need to solve this hash difference, but I'm curious about your approach.

Thanks,

Josh

On Fri, Oct 18, 2019 at 3:16 AM Sandro Mani <manisandro@gmail.com> wrote:

Hi

I'm packaging mingw-rust, and while everything compiled, the RPM build
fails with

BuildError: The following noarch package built differently on different
architectures: mingw32-rust-debuginfo-1.38.0-1.fc32.noarch.rpm
rpmdiff output was:
removed
/usr/i686-w64-mingw32/lib/rustlib/i686-pc-windows-gnu/lib/std-667f9119009aea97.dll.debug
added
/usr/i686-w64-mingw32/lib/rustlib/i686-pc-windows-gnu/lib/std-adb8e1a97c54d6f2.dll.debug
[etc]

So indeed I suppose the hashes used in the libraries vary depending on
various factors, possibly the architecture of the host system. Anyone
has an idea how to deal with this, or make the hashes stable between
host arches?

Thanks
Sandro
_______________________________________________
Rust mailing list -- rust@lists.fedoraproject.org
To unsubscribe send an email to rust-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/rust@lists.fedoraproject.org