| 1 Oct 2022 |
x10an14 | -> $ cargo tree --invert openssl-sys
openssl-sys v0.9.76
├── native-tls v0.2.10
│ ├── hyper-tls v0.5.0
│ │ └── reqwest v0.11.12
│ │ ├── assign-item-to-project-field v0.1.0 (/home/x10an14/Documents/sr.ht/assign-item-to-project-field)
│ │ └── graphql_client v0.11.0
│ │ └── assign-item-to-project-field v0.1.0 (/home/x10an14/Documents/sr.ht/assign-item-to-project-field)
│ ├── reqwest v0.11.12 (*)
│ └── tokio-native-tls v0.3.0
│ ├── hyper-tls v0.5.0 (*)
│ └── reqwest v0.11.12 (*)
└── openssl v0.10.42
└── native-tls v0.2.10 (*)
| 02:08:32 |
x10an14 | -> $ cargo tree --invert openssl
openssl v0.10.42
└── native-tls v0.2.10
├── hyper-tls v0.5.0
│ └── reqwest v0.11.12
│ ├── assign-item-to-project-field v0.1.0 (/home/x10an14/Documents/sr.ht/assign-item-to-project-field)
│ └── graphql_client v0.11.0
│ └── assign-item-to-project-field v0.1.0 (/home/x10an14/Documents/sr.ht/assign-item-to-project-field)
├── reqwest v0.11.12 (*)
└── tokio-native-tls v0.3.0
├── hyper-tls v0.5.0 (*)
└── reqwest v0.11.12 (*)
| 02:08:48 |
x10an14 | For completeness:
-> $ git diff Cargo.toml && echo -e "# Git diff of Cargo.toml above\\n---\\n# \`nix build\` and \`ldd\` invocation below" && nix build && ldd result/bin/*
Cargo.toml
10 ⋮ 10 │clap-verbosity-flag = "1"
11 ⋮ 11 │clap_complete_command = "0.3"
12 ⋮ 12 │color-eyre = "0.6"
13 ⋮ │graphql_client = "0.11"
⋮ 13 │graphql_client = { version = "0.11", features = ["reqwest-rustls"] }
14 ⋮ 14 │log = "0.4"
15 ⋮ │reqwest = { version = "0.11", features = ["json"] }
⋮ 15 │reqwest = { version = "0.11", features = ["json", "rustls-tls"] }
16 ⋮ 16 │serde = "1"
17 ⋮ 17 │serde_json = "1"
18 ⋮ 18 │tokio = { version = "1", features = ["macros", "rt-multi-thread", "fs"] }
# Git diff of Cargo.toml above
---
# `nix build` and `ldd` invocation below
warning: Git tree '/home/x10an14/Documents/sr.ht/assign-item-to-project-field' is dirty
linux-vdso.so.1 (0x00007ffef59a3000)
libssl.so.3 => not found
libcrypto.so.3 => not found
| 02:11:12 |
Zhaofeng Li | Sorry, on my phone, skipped over the Cargo.toml. | 02:12:21 |
Zhaofeng Li | You probably want default-features = false for reqwest | 02:12:37 |
x10an14 | Nps, here's the repo if you wanna take a closer look: https://git.sr.ht/~x10an14/assign-item-to-project-field/tree/9e47a140d950c5d21896f3cdb74ce2ccfdc3e324 | 02:12:51 |
x10an14 | Will attempt the default flag tip before I gotta sleep | 02:13:05 |
x10an14 | The default_features = false fixed it, many many thanks for all your help these last days. Now itis commit, push, and bedtime. | 02:20:58 |
| cbrewster joined the room. | 19:28:35 |
| 3 Oct 2022 |
| amesgen joined the room. | 23:21:40 |
| 4 Oct 2022 |
Mic92 | John Ericson: Have you looked into building rust targets in our default rustc before? | 16:29:11 |
Mic92 | I would be interested to build some sort ouf multi-output rustc derivation that also has webasm and musl. | 16:29:40 |
Alyssa Ross | joerg: I've briefly thought about it, and it would be complicated due to the need to have the libcs available for other targets. | 17:48:55 |
Alyssa Ross | I think it would be possible but not too easy. | 17:49:17 |
Mic92 | qyliss: at least webasm doesn't need one. | 17:54:20 |
Alyssa Ross | Yeah, that one would be easier. | 17:54:45 |
Alyssa Ross | In that case, you should be able to override pkgsStatic.buildPackages.rustc to also include the webassembly target with the existing package, right? | 17:55:32 |
Alyssa Ross | And then you'd have a compiler that could do glibc, musl, and webassembly. | 17:56:14 |
Alyssa Ross | If there are any targets that we can turn on "for free" like webassembly, adding those by default would make sense I think | 17:57:13 |
Alyssa Ross | That should just be a case of changing the default value of the package option, I think. | 17:58:00 |
x10an14 | Could I somehow configure a flake to perform its compilation steps in a (multi-layered) docker image? I can't see support for this (AFAIU) in dockerTools.
Ideally I'd like my flake defined default package to be built in a docker container, then having resulting binary copied out for any final/distroless container image (the latter of which dockerTools can produce just fine.) | 18:05:54 |
John Ericson | Mic92 Alyssa Ross is Rustc itself always multi-target? | 19:12:38 |
John Ericson | I wish we could just build the standard library and rustc with crate2nix and separately | 19:12:53 |
John Ericson | bypass rustbuild altogether | 19:13:03 |
Alyssa Ross | Ericson2314: you give it a list of targets to support | 19:18:54 |
John Ericson | Alyssa Ross: is that for building stadandard libraries or compiler features, though? | 19:23:08 |
John Ericson | my guess is just standard libraries | 19:23:21 |
Alyssa Ross | why would it be any different than clang? | 19:23:41 |
Alyssa Ross | and like, it has to be multi-target or cross-compiling wouldn't work | 19:24:21 |
Alyssa Ross | Because it's the same rustc that gets used for build and host. | 19:24:30 |