| 3 Jan 2025 |
 lzcunt | or just building pkgsCross.x86_64-linux-mlibc.mlibc | 17:29:06 |
| lzcunt | ah that's great | 17:29:17 |
| lzcunt | I think this is where gcc needs mlibc patches | 17:29:27 |
| lzcunt | time to go talk to the managarm people! | 17:29:36 |
| lzcunt | thanks very much | 17:30:34 |
| lzcunt | what's your git username and email? I'd like to list you as the author of the python and langCC patches | 17:31:32 |
 Artturin | In reply to @sananatheskenana:matrix.org
would it be out of scope for my future mlibc PR? should I send this seperately? Likely a separate staging PR because this might need some discussion on why it was even there | 17:31:58 |
| Artturin | Co-authored-by: Artturin <Artturin@artturin.com> | 17:32:00 |
| Artturin | * Artturin <Artturin@artturin.com> | 17:32:14 |
| lzcunt | on it | 17:37:05 |
| Artturin | Have the branch on the merge-base of staging and master so there's no merge conflicts or extra commits and no unnecessary rebuilds
git rebase --onto $(git merge-base staging master) HEAD~"$(git log master..HEAD --oneline | wc -l)" | 17:43:19 |
| Artturin | * Have the branch on the merge-base of staging and master so there's no merge conflicts or extra commits and no unnecessary rebuilds when building locally
git rebase --onto $(git merge-base staging master) HEAD~"$(git log master..HEAD --oneline | wc -l)" | 17:43:39 |
| lzcunt | wow that's a cool trick | 17:46:33 |
| lzcunt | I need master and staging to both be up to date tho right? | 17:46:53 |
| Artturin | They don't have to be up to date for what I said but they do if you don't want to use old revisions | 17:54:29 |
| Artturin | gitup . from git-repo-updater pulls all branches | 17:55:14 |
| lzcunt | I prefer to fetch all branches but manually fast forward (or rebase) them | 17:56:34 |
 emily | (jj rebase -d '::staging & ::master', jj git fetch 😎) | 17:56:35 |
| lzcunt | * I prefer to fetch all branches with git fetch upstream but manually fast forward (or rebase) them | 17:56:45 |
| lzcunt | https://github.com/NixOS/nixpkgs/pull/370683 patch is sent! | 18:02:37 |
| lzcunt | do you mind explaining what exactly the python patch does | 18:12:49 |
| lzcunt | * do you mind explaining what exactly the python patch does? for commit message purposes | 18:13:05 |
| lzcunt | is inputs' unused here? | 18:31:54 |
| Artturin | In reply to @sananatheskenana:matrix.org
do you mind explaining what exactly the python patch does? for commit message purposes See the commit message of https://github.com/NixOS/nixpkgs/commit/007088359e7a0b438f42387cb59c0479ba81df83 | 19:00:58 |
| 4 Jan 2025 |
 Tristan Ross | Trying to cross compile my Nix flake to RISC-V | 17:40:54 |
| Tristan Ross | Discovered lua-language-server does not like cross | 17:41:02 |
| Tristan Ross | lua-language-server> [35/37] Run test.
lua-language-server> build/linux/bin/bootstrap: line 1: ]
�: not found
lua-language-server> build/linux/bin/bootstrap: line 1: ELF�: not found
lua-language-server> build/linux/bin/bootstrap: line 2: s$: not found
lua-language-server> build/linux/bin/bootstrap: line 3: ���: not found
lua-language-server> build/linux/bin/bootstrap: line 0: : not found
lua-language-server> build/linux/bin/bootstrap: line 4: �
7: not found
lua-language-server> build/linux/bin/bootstrap: line 5: syntax error: unexpected word (expecting ")")
lua-language-server> build/linux/bin/bootstrap: line 1: @È‘@8
@@@@h���ttpC�j����0�0�0�����X[XkX: not found
lua-language-server> FAILED: build/linux/obj/test.stamp
lua-language-server> build/linux/bin/bootstrap bee.lua/test/test.lua --touch build/linux/obj/test.stamp
lua-language-server> [37/37] Copy build/linux/bin/bootstrap luamake
lua-language-server> ninja: build stopped: subcommand failed.
This is cursed
| 17:56:30 |
| Artturin | Likely using the wrong ld or something | 21:23:39 |
| Artturin | or that bootstrap binary is built for target | 21:24:05 |
| Artturin | * or that bootstrap binary is built for host | 21:24:06 |
