| 23 Nov 2025 |
 dramforever | okay at one point static pie didn't work on riscv*-linux but that should be fixed now. i think | 18:51:32 |
 Tristan Ross | In reply to @dramforever:matrix.org
"what flag" I think it's DF_1_PIE | 18:56:22 |
| Tristan Ross | In reply to @dramforever:matrix.org
okay at one point static pie didn't work on riscv*-linux but that should be fixed now. i think When was it fixed? | 18:56:40 |
| Tristan Ross | Because I did run into the problem like 2 weeks ago | 18:56:57 |
| dramforever | oh hmm interesting | 20:22:10 |
| dramforever | i didn't think it mattered? | 20:22:26 |
| dramforever | do you mean a go program? | 20:22:38 |
| Tristan Ross | GCC & patchelf in the bootstrap-tools | 20:25:30 |
| Tristan Ross | But the go error is preventing me from building for the system lol | 20:25:49 |
| dramforever | wasn't that a non-pie problem? | 20:26:38 |
| Tristan Ross | GCC has a PIE address but the flag in the ELF header isn't set | 20:26:58 |
| Tristan Ross | So vm.mmap_min_addr is higher than the PHDR address | 20:27:09 |
| Tristan Ross | Which causes the kernel to fail the mmap of the PHDR | 20:27:21 |
| Tristan Ross | Patchelf was fixed at some point and that one fixes itself after updating the bootstrap-tools but GCC is still broken | 20:28:06 |
| dramforever | no no no a normal PIE would start at address 0 | 20:29:05 |
| dramforever | that one has file type ET_EXEC | 20:29:16 |
| dramforever | pies have ET_DYN but also DF_1_PIE | 20:29:34 |
