Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Rust error: "failed to install component: 'rust-std-aarch64-unknown-linux-gnu', detected conflict" #728

Closed
jforissier opened this issue Jan 29, 2024 · 2 comments
Closed

Rust error: "failed to install component: 'rust-std-aarch64-unknown-linux-gnu', detected conflict" #728

jforissier opened this issue Jan 29, 2024 · 2 comments
Labels
Stale

Comments

@jforissier
Copy link
Contributor

The CI job "QEMUv8_Hafnium_check" in optee_os (link) fails with:

2024-01-29T14:33:04.1739690Z error: failed to install component: 'rust-std-aarch64-unknown-linux-gnu', detected conflict: 'lib/rustlib/aarch64-unknown-linux-gnu/lib/libaddr2line-1b440c2cf263d456.rlib'

See attached log.txt.
@jforissier jforissier mentioned this issue Jan 29, 2024
Merged
b49020 added a commit to b49020/build that referenced this issue Jan 30, 2024
@b49020
qemu_v8: Disable Rust examples by default
89d806c 
There has been random CI build failures reported while building Rust
examples. Most of them seems like conflicts with buildroot provided Rust
toolchain. So until those are resolved, disable default Rust examples
build for now to get the CI passing successfully.

Link: OP-TEE#727
Link: OP-TEE#728
Acked-by: Etienne Carriere <[email protected]>
Acked-by: Jerome Forissier <[email protected]>
Acked-by: Jens Wiklander <[email protected]>
Signed-off-by: Sumit Garg <[email protected]>
jforissier pushed a commit that referenced this issue Jan 30, 2024
@b49020 @jforissier
qemu_v8: Disable Rust examples by default
6e4656d 
There has been random CI build failures reported while building Rust
examples. Most of them seems like conflicts with buildroot provided Rust
toolchain. So until those are resolved, disable default Rust examples
build for now to get the CI passing successfully.

Link: #727
Link: #728
Acked-by: Etienne Carriere <[email protected]>
Acked-by: Jerome Forissier <[email protected]>
Acked-by: Jens Wiklander <[email protected]>
Signed-off-by: Sumit Garg <[email protected]>
@b49020
Copy link
Contributor

b49020 commented Feb 5, 2024

Should be fixed by: #731

b49020 added a commit to b49020/build that referenced this issue Feb 7, 2024
@b49020
optee_rust_examples_ext: Fix Rust toolchain conflicts
2523831 
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Signed-off-by: Sumit Garg <[email protected]>
@b49020 b49020 mentioned this issue Feb 7, 2024
Merged
b49020 added a commit to b49020/build that referenced this issue Feb 7, 2024
@b49020
optee_rust_examples_ext: Fix Rust toolchain conflicts
861effe 
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Signed-off-by: Sumit Garg <[email protected]>
b49020 added a commit to b49020/build that referenced this issue Feb 8, 2024
@b49020
optee_rust_examples_ext: Fix Rust toolchain conflicts
4ee2990 
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Signed-off-by: Sumit Garg <[email protected]>
b49020 added a commit to b49020/build that referenced this issue Feb 8, 2024
@b49020
optee_rust_examples_ext: Fix Rust toolchain conflicts
5e20907 
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Signed-off-by: Sumit Garg <[email protected]>
b49020 added a commit to b49020/build that referenced this issue Feb 8, 2024
@b49020
optee_rust_examples_ext: Fix Rust toolchain conflicts
e202ddf 
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Signed-off-by: Sumit Garg <[email protected]>
b49020 added a commit to b49020/build that referenced this issue Feb 8, 2024
@b49020
optee_rust_examples_ext: Fix Rust toolchain conflicts
746252e 
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Signed-off-by: Sumit Garg <[email protected]>
b49020 added a commit to b49020/build that referenced this issue Feb 9, 2024
@b49020
optee_rust_examples_ext: Fix Rust toolchain conflicts
60363f5 
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Signed-off-by: Sumit Garg <[email protected]>
b49020 added a commit to b49020/build that referenced this issue Feb 9, 2024
@b49020
optee_rust_examples_ext: Fix Rust toolchain conflicts
5498d02 
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Tested-by: Jerome Forissier <[email protected]>
Signed-off-by: Sumit Garg <[email protected]>
b49020 added a commit to b49020/build that referenced this issue Feb 9, 2024
@b49020
optee_rust_examples_ext: Fix Rust toolchain conflicts
83c35ee 
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] OP-TEE#727
Fixes: [2] OP-TEE#728
Acked-by: Jerome Forissier <[email protected]>
Tested-by: Jerome Forissier <[email protected]>
Signed-off-by: Sumit Garg <[email protected]>
jforissier pushed a commit that referenced this issue Feb 9, 2024
@b49020 @jforissier
optee_rust_examples_ext: Fix Rust toolchain conflicts
f0a2eef 
Buildroot provides its own Rust toolchain for various Linux user-space
components. However, that toolchain doesn't support nightly version of
Rust complier which we need for OP-TEE Rust examples for the time being.

Due to two separate Rust toolchains being used for different buildroot
components, there are conflicts [1] [2] observed leading to CI errors.
In order to fix them enable OP-TEE specific Rust toolchain specifically
to build OP-TEE Rust examples rather than enabling it for the entire
buildroot build.

Fixes: [1] #727
Fixes: [2] #728
Acked-by: Jerome Forissier <[email protected]>
Tested-by: Jerome Forissier <[email protected]>
Signed-off-by: Sumit Garg <[email protected]>
@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 7, 2024

This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time.

@github-actions github-actions bot added the Stale label Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jforissier @b49020