21 Oct 2024 |
Alyssa Ross | In reply to @luckytethys:matrix.org Oh, in that case it would be a lot easier. That might be feasible. Please do try to upstream it though! | 15:50:24 |
emily | In reply to @qyliss:fairydust.space I believe it'll build an as for targetPlatform right. which seems… misleading | 15:50:56 |
emily | given that you are asking for all the targets, and probably expect targetPlatform to be irrelevant | 15:51:11 |
Alyssa Ross | Yes, I agree. | 15:51:18 |
emily | which is an argument for building all the as es in that package IMO | 15:51:20 |
Alyssa Ross | Possibly | 15:51:26 |
Alyssa Ross | There's also something to be said for doing what upstream does | 15:51:50 |
Alyssa Ross | But you may be right that that would make more sense overall. | 15:51:58 |
emily | I'm guessing that what upstream does is mostly not expect people to do this | 15:52:17 |
jh-devv 🏳️⚧️ | How do I add the binaries in from the image in dockerTools.runWithOverlay postMount?
| 16:02:03 |
jh-devv 🏳️⚧️ | * How do I add the binaries from the image to the path in dockerTools.runWithOverlay postMount?
| 16:05:42 |
Tethys Svensson | Alyssa Ross: First problem with upstreaming is that is that I don't know how to detect whether a given binary has multi-arch support, or whether it has sufficient multi-arch support to support the cases needed by pwntools. I don't think trying to figure this out is a good use of my time. I would much prefer to either have an architecture-specific objdump in nixpkgs or hardcode a patch to pwntools that forces the use of a known-good multi-arch version. | 16:11:54 |
Tethys Svensson | So the nixpkgs-only patch would be much easier to write and to maintain than an upstream-version that tries to detect whether the multi-arch version is multi-arch enough. | 16:13:12 |
Alyssa Ross | Doesn't pwntools already have to do this for the other binutils binaries that might or might not be multi-arch? | 16:14:12 |
Tethys Svensson | Not really | 16:14:31 |
Tethys Svensson | It uses a few host-specific binaries like gdb and cpp. For gdb it just hopes that it has multi-arch support (also, for gdb you mostly just need the host-specific version anyways). For cpp the architecture doesn't actually matter. | 16:15:34 |
Tethys Svensson | For the other tools mentioned it tries to find an architecture-specific version and if it can't then it gives up | 16:16:03 |
Tethys Svensson | The only special-case is that it tries the host-specific version when the target architecture is sufficiently close to the host architecture. | 16:16:23 |
Alyssa Ross | Could it just fall back if it doesn't find the architecture-specific nersion? | 16:21:18 |
Tethys Svensson | It has a fallback where it tries to detect whether it is on a system where it knows how to install a architecture-specific binutils and then suggests how to do that | 16:22:14 |
Tethys Svensson | Also, the error messages would be absolutely cursed if it tried to use a version that doesn't work | 16:22:44 |
9999years | something going on with nix.ci; cert errors + File not found. + Check ./stats.php on the homepage https://monitoring.nix.ci/dashboard/db/ofborg | 16:29:32 |
emily | https://ofborg.org/ is the canonical domain again now. though https://monitoring.ofborg.org/dashboard/db/ofborg also doesn't seem to be working | 16:30:09 |
jh-devv 🏳️⚧️ | In reply to @jh-devv:matrix.org
How do I add the binaries from the image to the path in dockerTools.runWithOverlay postMount?
could anybody help with this? | 16:39:31 |
SomeoneSerge (utc+3) | Ah so ofborg is having a moment? Noticed @ofborg eval is getting no reaction | 16:43:46 |
Lily Foster | In reply to @ss:someonex.net Ah so ofborg is having a moment? Noticed @ofborg eval is getting no reaction it should have put it in the queue. how long has it been? the eval queue depth is pretty big so it'll be a while before it gets to it | 16:44:54 |
SomeoneSerge (utc+3) | One 25' ago and one 49' | 16:45:34 |
emily | you gotta be a lot more patient than that | 16:45:50 |
Lily Foster | yeah it'll probably be longer than that still | 16:45:58 |
SomeoneSerge (utc+3) | 👌 | 16:46:09 |