-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Configure not detecting compiler. #11648
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
Comments
Have you tried compiling a simple program to make sure it works? Something like |
-m32 does not work, complains about Have you tried compiling a simple program to make sure it works? Something — |
Closing, it sounds like you need to install the 32-bit compiler libraries and headers for your system. I think that on ubuntu you can find this in the You can also not configure a cross compiler by just running |
…archo [`unnecessary_to_owned`]: catch `to_owned` on byte slice to create temporary `&str` Closes rust-lang#11648 Detects the pattern `&String::from_utf8(bytes.to_vec()).unwrap()` and suggests `core::str::from_utf8(bytes).unwrap()`, which avoids the unnecessary intermediate allocation. I decided to put this in the existing `unnecessary_to_owned` lint (rather than creating a new lint) for a few reasons: - we get to use some of its logic (for example, recognizing any of the functions in the `to_owned` family, e.g. `to_vec`) - the actual inefficient operation that can be avoided here is the call to `.to_vec()`, so this is in a way similar to the other cases caught by `unnecessary_to_owned`, just through a bunch of type conversions - we can make this more "generic" later and catch other cases, so imo it's best not to tie this lint specifically to the `String` type changelog: [`unnecessary_to_owned`]: catch `&String::from_utf8(bytes.to_vec()).unwrap()` and suggest `core::str::from_utf8(bytes).unwrap()`
On attempting to compile latest git version:
Output of ./configure:
Output is the same with --disable-clang.
Output of uname -a:
The text was updated successfully, but these errors were encountered: