| 13 Jul 2025 |
 QuadRadical (Ping) | the issue is in the crate right? | 20:33:32 |
| QuadRadical (Ping) | thats what you said? | 20:33:39 |
| QuadRadical (Ping) | the devicemapper crate? | 20:33:45 |
 Grimmauld (any/all) | from what i can tell (realy i am not good with this) it seems either the pkg-config path is a little broken or its using the wrong ld | 20:34:56 |
| Grimmauld (any/all) | linker says "skipping incompatible", the log says /nix/store/pbqah1qk4b5y14fqinr1h8zvhqy71v81-gcc-wrapper-14.3.0/bin/cc. The compiler should probably be more like /nix/store/xspnj9pmwz481xdfvwh365b6fzgch4k9-aarch64-unknown-linux-gnu-gcc-wrapper-14.2.1.20250322/bin/aarch64-unknown-linux-gnu-gcc, but i am not sure how to force that | 20:38:13 |
| QuadRadical (Ping) | hmm i see | 20:44:05 |
| QuadRadical (Ping) | So putting lvm2 in depsBuildBuild like emily said isn't required, you think? | 20:44:34 |
 emily | if it's using the wrong compiler then that's what needs fixing rather than the architecture of the dep | 20:44:52 |
| emily | it just looked like a build script thing to me | 20:45:02 |
| QuadRadical (Ping) | ah i see thank you | 20:45:15 |
| Grimmauld (any/all) | dunno, emily knows more than me | 20:45:21 |
| Grimmauld (any/all) | to me the compiler looked wonky, but i am also not super familiar with the internals of the cargo builder and how it wraps gcc/binutils | 20:45:51 |
| emily | the fix is probably simple (set one env variable, patch a few lines) | 20:45:59 |
| emily | it just depends on what the crate is actually doing | 20:46:03 |
| QuadRadical (Ping) | I see, thank you | 20:46:09 |
| emily | check its build.rs perhaps | 20:46:13 |
| Grimmauld (any/all) | (pain is the fact the crate is likely burried in the dep tree, can we actually patch crates?) | 20:46:44 |
| emily | we can, in the vendor directory | 20:47:39 |
| emily | it doesn't scale well when they have multiple consumers though | 20:47:45 |
| Grimmauld (any/all) | interesting! didn't know that, thats useful | 20:48:01 |
| QuadRadical (Ping) | uh i have no idea what to do | 20:49:11 |
| QuadRadical (Ping) | ill check the build.rs as suggested | 20:49:15 |
| emily | https://github.com/stratis-storage/devicemapper-rs/commit/2be7e2e79448b58072690d62b5b47a401c637220 https://github.com/stratis-storage/devicemapper-rs/commit/2717eff0b5d5373af62b3d14d8edcbfe2c3a1b87 | 20:49:18 |
| emily | mentions cross | 20:49:19 |
| emily | I don't really understand why the Cargo metadata would be a problem though… smells like they're doing something wrong | 20:50:13 |
| emily | QuadRadical (Ping / Reply): did you try bumping to 1.2.0 | 20:51:37 |
| emily | https://github.com/stratis-storage/devicemapper-rs/issues/965 lol yeah okay this is kind of dumb | 20:53:03 |
| QuadRadical (Ping) | thin-provisioning-tools is already at 1.2.0 | 20:54:12 |
| emily | oh sorry, I was checking on an old branch | 20:54:20 |
| QuadRadical (Ping) | no worries | 20:54:35 |
