| 10 Nov 2025 |
 ElvishJerricco | Hypothesis: When you do GOARCH= go run ..., it was previously using some linker other than $CC, and it was successfully building a binary for the build platform. But now with the PIE change, it's trying to use $CC for its linker, and expecting that to be a valid linker for the build platform, i.e. in this case an x86_64 linker that it can pass -m64 to. So even if it wasn't making the -m64 mistake, it would still fail trying to link an x86_64 binary with an aarch64 linker. | 11:15:57 |
| ElvishJerricco | Does that sound plausible? | 11:16:05 |
| ElvishJerricco | Ok, yea, that's exactly what's happening, and fixing it requires a patch. | 15:45:04 |
| ElvishJerricco | Which I guess means I can't get this fix into staging-next | 15:45:46 |
| ElvishJerricco | well, I guess if I add the patch conditionally (only when we're cross compiling), it's not a mass rebuild for non-cross, so it could go to staging-next? | 15:50:38 |
| ElvishJerricco | is that even worth it? | 15:51:07 |
 K900 | Doable | 16:00:36 |
