rust-analyzer: Bump to release 2021-09-13

[shadmansaleh]

No description provided.

[shadmansaleh]

Anyone with experience in rust ?

Compiling hir_ty v0.0.0 (/home/builder/.termux-build/rust-analyzer/src/crates/hir_ty)
error[E0658]: use of unstable library feature 'control_flow_enum': new API
 --> crates/hir_ty/src/method_resolution.rs:5:17
  |
5 | use std::{iter, ops::ControlFlow, sync::Arc};
  |                 ^^^^^^^^^^^^^^^^
  |
  = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

Does this mean rust nightly compiler is required to compile this ?

[shadmansaleh]

Well can't really enable unstable features in stable compiler .

Looks like the type ops::ControlFlow was stabilized in rust-lang/rust#85608 .We have newer rust compiler than that right ?

Edit:
No we don't it was released in 1.55.0 we have 1.53.0 so this wont compile until rust is bumped to 1.55.0

1.55 was released a week ago and since upgrading to 1.54 failed I think this pr will remain draft for a while.

[shadmansaleh]

Any idea why result of

curl -s fileurl | sha256sum

is different different then

curl -Lo file fileurl
sha256sum file

??

How do you get sha256 of file for package ?

[ghost]

How do you get sha256 of file for package ?

cd ./packages/${YOUR_PACKAGE}
(source build.sh 2>/dev/null; curl -LO "$TERMUX_PKG_SRCURL")
sha256sum "file"

Use -L for curl because of possible redirects.

You may also use script ./scripts/bin/update-checksum

[shadmansaleh]

@xeffyr Thanks . That makes sense it wasn't getting redirected.

One off topic question . Is there a way to disable a step for a package . For example I'm trying to build a c/cpp program . You just need to run make and configure step makes no sense and causes the build to fail . Can I some how say the builder to skip configure and just run the make step ?

[ghost]

Can I some how say the builder to skip configure and just run the make step ?

Just define empty configure step

termux_step_configure() {
	:
}

[shadmansaleh]

For now lets keep auto_update out of this pr since it'll require changes to core scripts and possibly to other packages too depending on how we do it .

This can be merged without it.