| # 03:31:04 | Buglouse | quits : Ping timeout: 252 seconds |
| # 04:05:50 | Buglouse | joins #crosstool-ng |
| # 07:04:17 | mnt_real | quits : Quit: Ex-Chat |
| # 07:09:21 | smartin | joins #crosstool-ng |
| # 12:03:17 | y_morin | joins #crosstool-ng |
| # 15:30:13 | y_morin | quits : Quit: Going back home... :-) |
| # 16:39:30 | y_morin | joins #crosstool-ng |
| # 16:43:45 | Buglouse | quits : Ping timeout: 260 seconds |
| # 16:49:23 | Buglouse | joins #crosstool-ng |
| # 16:49:32 | KAeL | joins #crosstool-ng |
| # 16:49:45 | y_morin | KAeL: heya! |
| # 16:49:52 | KAeL | ! |
| # 16:50:42 | y_morin | So, as you said, there is a slight adaptation to be made so that crostool-NG accepts a pre-filed directory with the kernel sources. |
| # 16:50:58 | KAeL | should be easy |
| # 16:51:20 | y_morin | Yep, should. |
| # 16:51:31 | KAeL | most of the work is to change text in menuconfig/help to say it can be tarball OR directory |
| # 16:51:37 | KAeL | :) |
| # 16:52:40 | y_morin | Mostly. Fact is, if this is a dir, then the script has to be modified to use that dir, and not do a tar xjf "${tarball}" |
| # 16:52:57 | y_morin | So this is not so easy. Not complex, but not trivial either... |
| # 16:56:31 | KAeL | ok ok |
| # 18:17:29 | kos_tom | ah, yes, having this would be useful. |
| # 18:20:36 | mnt_real | joins #crosstool-ng |
| # 18:25:30 | y_morin | kos_tom, KAeL: I have some changes to finish on Mercurial, and then I switch back to hacking crosstool-NG. That should happen by the end of the week... |
| # 18:40:00 | KAeL | y_morin: I'll send you a patch tomorrow |
| # 18:40:13 | y_morin | KAeL: Oh! Nice! :-) |
| # 18:43:48 | KAeL | then I will patch buildroot to use this :) |
| # 18:44:51 | y_morin | is now known as: y_morin|away |
| # 19:23:05 | smartin | quits |
| # 20:08:50 | smartin | joins #crosstool-ng |
| # 20:37:28 | smartin | quits : Ping timeout: 252 seconds |
| # 21:19:34 | y_morin|away | is now known as: y_morin |
| # 23:33:03 | y_morin | quits : Quit: Nighty Nite... |