-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compiling with cross set to target armv7-unknown-linux-gnueabihf
causes issues with try_map_coords_inplace
.
#1010
Comments
armv7-unknown-linux-gnueabihf
causes issues with try_map_coords_inplace.armv7-unknown-linux-gnueabihf
causes issues with try_map_coords_inplace
.
Fork with problematic compilation portion panic-ing instead: https://github.com/AlterionX/geo/tree/monkeypatch |
Thank you for providing the reproduction details, but I'm still having trouble reproducing this. Note that I am running on macos. I'm not very familiar with cross, but I installed it and everything seemed to just work.
Do things work for you on rust stable? One thing I'll note is that error is originating inside of some deprecated code that I think we could probably delete at this point. Do you want to try building from this branch which removes the deprecated code? https://github.com/georust/geo/tree/mkirk/remove-deprecated-map-coords |
I'm running on WSL Ubuntu, architecture is x86_64. If you're on Mac, perhaps it's not causing a problem due to the mac's architecture being ARM? I would expect that changing the branch to the version listed to resolve the issues. |
Ah, rustc fixed something on their side. Closing. |
Another user is hitting this issue @AlterionX - can you clarify, were you able to get this working on an updated nightly? (And which version was it that worked for you?) |
Yep, I was able to get it working on nightly @michaelkirk . Not sure which version, but I assume 2023-04-20 I ended up resetting my PC so might take a bit to check the most recent nightly though. |
This might be a bug on our side, according to rust-lang/rust#110475. |
Started hitting this as well installing a crate that depends on
I'll be honest I had not run into the |
@worace the recursion limit is a red herring. There might have been a bug in some Unfortunately, the easiest fix is probably pinning an older nightly (or using |
ok good to know. I'll try the next release of |
This has been published just now with https://crates.io/crates/geo/0.25.0 |
* chore: Update `geo` to use latest stable Rust georust/geo#1010 * Revert "chore: added toolchain toml to pin version (#1749)" This reverts commit a63cb2d. * Revert "pin toolchain version to RUSTC_VERSION: 1.70.0 instead of stable (#1748)" This reverts commit eba9ab9.
Previously used version 0.23 was carrying a [recursive declaration issue][1] Fixed since geo 0.25 as mentioned in [related issue][2] [1]: rust-lang/rust#110475 [2]: georust/geo#1010 Signed-off-by: Nicolas Buffon <nicolas.buffon@orange.com>
Repro repo: https://github.com/AlterionX/bug-repro/tree/cross-geo-compilation
Running
cross build --release
fails to compile with the following:cross build
,cargo build
, andcargo build --release
all work.cross
is targetingarmv7-unknown-linux-gnueabihf
.cargo
is targetingx86_64-unknown-linux-gnu
. I have not tested with other architectures.Bumping up the recusion limit as suggested simply increases the number of
&
s, suggesting an actual error?The text was updated successfully, but these errors were encountered: