15 Apr 2024 |
emilgardis | I think you'll need to uninstall the toolchain and reinstall | 21:17:55 |
emilgardis | or hmm | 21:18:08 |
emilgardis | you're on fedora, I've seen something similar before | 21:18:17 |
emilgardis | ah yes: https://github.com/cross-rs/cross/issues/1470#issuecomment-2045457819 | 21:19:37 |
emilgardis | something about mounts and/or selinux | 21:20:15 |
jfaz1 | In reply to @emilgardis:matrix.org ah yes: https://github.com/cross-rs/cross/issues/1470#issuecomment-2045457819 I tried moving it to a different location and it still persists 😠| 21:24:49 |
jfaz1 | It's a small test project, if it helps I can zip it up | 21:24:59 |
emilgardis | can you try uninstalling the toolchain | 21:25:12 |
emilgardis | that won't help | 21:25:14 |
emilgardis | try replicating the problem in a completely new project | 21:25:24 |
emilgardis | I'm sure you'll see the same thing | 21:25:38 |
jfaz1 | Nope.. I think I'm just gonna try rolling with armv6 since that's my target anyways, though I think I'll have to compile the libraries from source right? | 23:29:42 |
16 Apr 2024 |
| Sch joined the room. | 05:34:18 |
jfaz1 | Got it working with a custom Dockerfile, thanks for the help! | 06:36:24 |
17 Apr 2024 |
| sarath08071994 joined the room. | 05:33:02 |
18 Apr 2024 |
| Charles R. Tyrrell joined the room. | 14:57:18 |
Charles R. Tyrrell | Guys, can you help me with my GitLab CI issues? I don't understand how I should write the configuration to run the aarch64 image and Rust latest, because in this case commands like rustup and others don't work.
```
.build:
stage: build # extends:
# - .host:debian script:
- rustup --version && rustc --version && cargo --version - rustup target add $TARGET
- cargo build --release --locked --target=$TARGET
aarch64-unknown-linux-gnu: image: ghcr.io/cross-rs/aarch64-unknown-linux-gnu:edge-centos extends: - .build variables: TARGET: aarch64-unknown-linux-gnu
``` | 15:13:04 |
emilgardis | Charles R. Tyrrell: have you seen https://github.com/cross-rs/cross/wiki/FAQ#gitlab-ci? There's also this way of doing it | 16:50:46 |
Charles R. Tyrrell | Thank you bro | 16:52:20 |
19 Apr 2024 |
| cwqb joined the room. | 20:50:38 |
22 Apr 2024 |
Sir Mangler | How can I get the full log from a pre-build? | 11:30:48 |
23 Apr 2024 |
| taotree joined the room. | 11:34:01 |
taotree | Could someone help me? I've been trying for some time. I want to build for --target aarch64-unknown-linux-musl when the host is aarch64-unknown-linux-gnu. I found issue 975 and the docker image on docker hub, but it's still looking for x86_64 or amd64. | 12:19:14 |
taotree | Redacted or Malformed Event | 12:31:40 |
taotree | In reply to @taotree:matrix.org Could someone help me? I've been trying for some time. I want to build for --target aarch64-unknown-linux-musl when the host is aarch64-unknown-linux-gnu. I found issue 975 and the docker image on docker hub, but it's still looking for x86_64 or amd64. * It's erroring with: "docker: image with reference docker.io/ahuszagh/aarch64-cross:aarch64-unknown-linux-musl was found but does not match the specified platform: wanted linux/amd64, actual: linux/arm64." but what is specifying amd64? I do want arm64. | 12:32:03 |
taotree | It's erroring with: "docker: image with reference docker.io/ahuszagh/aarch64-cross:aarch64-unknown-linux-musl was found but does not match the specified platform: wanted linux/amd64, actual: linux/arm64."
but what is specifying amd64? I do want arm64. | 12:40:13 |
taotree | I think I figured it out finally. This Cross.toml seems to do it:
[build]
default-target = "aarch64-unknown-linux-musl"
[target.aarch64-unknown-linux-musl]
image.name = "ahuszagh/aarch64-cross:aarch64-unknown-linux-musl"
image.toolchain = ["aarch64-unknown-linux-musl"]
| 12:40:56 |
25 Apr 2024 |
| @sergiomassa:sibnsk.net removed their profile picture. | 22:43:11 |
| @sergiomassa:sibnsk.net left the room. | 23:28:15 |
26 Apr 2024 |
| Federico Damián Schonborn changed their profile picture. | 14:48:54 |