| # 01:05:16 | cpackham | quits : Ping timeout: 256 seconds |
| # 01:30:43 | cpackham | joins #crosstool-ng |
| # 02:04:31 | Trel | cpackham: I was trying to look at the examples in the GitHub actions you mentioned because it wasn't working. The toolchain section looks blank to me there. |
| # 02:06:30 | Trel | Are those private or at least not available logged out? |
| # 02:08:34 | cpackham | The action runs themselves require you to log in. But you can still look at the actions configs in the repo |
| # 02:09:27 | cpackham | The workflow is basically |
| # 02:11:38 | cpackham | ct-ng x86_64-w64-mingw32 && ct-ng build && export PATH=/home/foo/x-tools/x86_64-w64-mingw32/bin && ct-ng x86_64-w64-mingw32,x86_64-pc-linux-gnu && ct-ng build |
| # 02:12:40 | cpackham | sorry that should be `export PATH="$HOME/x-tools/x86_64-w64-mingw32/bin:$PATH"` (otherwise a bunch of stuff will disappear on you) |
| # 02:14:10 | cpackham | Part of the magic is that the `x86_64-w64-mingw32,x86_64-pc-linux-gnu` config sets `CT_HOST="x86_64-w64-mingw32"` which means it knows to use `x86_64-w64-mingw32-gcc` instead of `gcc` when building something |
| # 02:23:05 | Trel | Is that required when defining it via menuconfig? I thought I saw the option to set it when I picked canadian in the menu. |
| # 02:23:33 | Trel | It looked like it was picking up the right one, I think? |
| # 02:37:56 | cpackham | I don't think there's anything that sets CT_HOST magically but if your config has it in it then it it'll be there |
| # 02:48:00 | Trel | I'll double check when I'm back at the machine the value what I set changed. |
| # 03:33:37 | Trel | *what the value I set (no clue how I scrambled the words) |
| # 04:06:53 | cpackham | quits : Ping timeout: 240 seconds |
| # 18:31:10 | milkylainen | 2.39 looks like it deprecates crypt completely, right? |