https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216143
Jean-Sébastien Pédron <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress CC| |[email protected] --- Comment #1 from Jean-Sébastien Pédron <[email protected]> --- Hi! I started to look into this. == Updating lang/rust-nightly == I'm updating lang/rust-nightly to a recent snapshot and add support for i386 at the same time. This is not directly related to this issue but will help to make sure we don't have regression. I'm currently testing the port in Poudriere for HEAD/amd64 and 11.0/i386. == Cargo on i386 == I'm updating devel/cargo to 0.15.0 and add i386 support at the same time. There cargo prebuilt binaries available for FreeBSD/i386 since last October, I missed that. I'm currently testing the port in Poudriere for HEAD/amd64. Unfortunately, I can't test 11.0/i386 because cargo(1) for i386 segfaults on amd64. The executable runs successfully in ref11-i386. I will try to build the port there. == Rust and Cargo on !x86 == Finally, I started to look for guides to bootstrap Rust and Cargo on unsupported hosts. I'm going to take aarch64 as the first victim. I found the following article from someone who did several ports of Rust: https://www.reddit.com/r/rust/comments/5ag60z/how_do_i_bootstrap_rust_to_crosscompile_for_a_new/ The following article might be useful too; I'm not sure yet: http://os.phil-opp.com/cross-compile-libcore.html I will keep you posted. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "[email protected]"
