Currently, if a version upgrade happens upstream on the user's rustc before the user cleans their cargo git cache, the build script will download the new version of rust, and merge the tarball with the existing working directory when unzipping.
If the versions differ, the build script should delete the existing rust directory, and unzip the tarball in to a clean directory instead.
This is, at the very least, the root cause of hackndev/zinc#336, and potentially many other libcore-related compilation issues.
Currently, if a version upgrade happens upstream on the user's rustc before the user cleans their cargo git cache, the build script will download the new version of rust, and merge the tarball with the existing working directory when unzipping.
If the versions differ, the build script should delete the existing
rust
directory, and unzip the tarball in to a clean directory instead.This is, at the very least, the root cause of hackndev/zinc#336, and potentially many other
libcore
-related compilation issues.