| # 06:25:58 | mingwandroid | joins #crosstool-ng |
| # 07:24:11 | diorcety | joins #crosstool-ng |
| # 07:54:35 | diorcety | quits : Read error: Connection reset by peer |
| # 07:55:56 | diorcety | joins #crosstool-ng |
| # 08:30:34 | diorcety | quits : Read error: Connection reset by peer |
| # 08:31:39 | diorcety | joins #crosstool-ng |
| # 10:29:03 | Net147 | quits : Ping timeout: 244 seconds |
| # 10:30:48 | Net147 | joins #crosstool-ng |
| # 12:15:17 | diorcety | quits : Read error: Connection reset by peer |
| # 17:38:56 | diorcety | joins #crosstool-ng |
| # 18:00:33 | luc4 | joins #crosstool-ng |
| # 18:50:48 | aquarat_ | joins #crosstool-ng |
| # 18:50:48 | aquarat | quits : Read error: Connection reset by peer |
| # 20:44:38 | aquarat_ | is now known as: aquarat |
| # 20:45:15 | y_morin | joins #crosstool-ng |
| # 21:04:24 | dsmith-work | joins #crosstool-ng |
| # 21:31:46 | dsmith-work | Probably a FAQ: So what is the best way to distribute a built toolchain. I kind of expecting somewthin like: ct-ng DESTDIR={somewhere} install |
| # 21:32:17 | dsmith-work | And then I can tar up {somewhere} for other people/machines on my team. |
| # 21:33:41 | dsmith-work | Building a toolchain takes quite a while. |
| # 21:33:57 | dsmith-work | Would be nice to only do that once. |
| # 21:34:43 | dsmith-work | Looks like "tarball" was supposed to do something like that, but is broken? |
| # 21:39:59 | enunes | dsmith-work: you can change the output dir in the config CT_PREFIX_DIR , and you can tar that directory later to distribute the toolchain |
| # 21:42:32 | dsmith-work | enunes: Thanks |
| # 21:47:58 | diorcety | quits : Read error: Connection reset by peer |
| # 21:52:53 | y_morin | quits : Quit: Nighty Night! (after two long and exhausting work days...) |
| # 21:58:30 | enunes | quits : Quit: leaving |
| # 22:15:03 | enunes | joins #crosstool-ng |