| # 00:17:50 | codyps | quits : Ping timeout: 252 seconds |
| # 00:41:11 | devcoder | quits : Quit: devcoder |
| # 04:58:40 | alan_o | quits : Quit: Leaving |
| # 06:38:29 | sspiff | joins #crosstool-ng |
| # 07:06:20 | Net147 | joins #crosstool-ng |
| # 07:14:24 | smartin | quits : Quit: leaving |
| # 07:56:57 | smartin | joins #crosstool-ng |
| # 09:03:50 | Net147 | quits : Quit: HydraIRC -> http://www.hydrairc.com <- In tests, 0x09 out of 0x0A l33t h4x0rz prefer it :) |
| # 11:49:06 | sspiff | quits : Remote host closed the connection |
| # 11:49:34 | sspiff | joins #crosstool-ng |
| # 11:49:34 | sspiff | quits : Changing host |
| # 11:49:34 | sspiff | joins #crosstool-ng |
| # 15:18:38 | codyps | joins #crosstool-ng |
| # 16:48:47 | codyps | quits : Ping timeout: 246 seconds |
| # 16:49:23 | codyps | joins #crosstool-ng |
| # 16:56:35 | y_morin | joins #crosstool-ng |
| # 17:15:40 | aaribaud | hi all, sorry for the repeat. I have just installed crosstool-ng to experiment with gcc in order to analyze an issue I've been handed as the U-Boot ARM custodian. Therefore I may need to patch gcc and rebuild it several times, and I'm a bit lost as how this should be done within crosstool-ng. For instance, should I create a local patch repository, or should I directly patch under .build once a first ct-ng build is done? A |
| # 18:08:39 | smartin | quits : Quit: leaving |
| # 19:15:48 | smartin | joins #crosstool-ng |
| # 19:27:50 | imMute | quits : Ping timeout: 246 seconds |
| # 20:41:34 | y_morin | aaribaud: hello! |
| # 20:41:44 | aaribaud | y_morin: hello |
| # 20:42:12 | y_morin | aaribaud: crosstool-NG was not designed for this task. However, the best bet in your case would be to patch gcc manually before each build. |
| # 20:42:35 | y_morin | aaribaud: what I would suggest is: |
| # 20:42:46 | y_morin | 1) do a full build |
| # 20:42:54 | y_morin | 2) cd .build/src |
| # 20:43:06 | y_morin | 3) cp -a gcc-X.Y.Z gcc-X-Y-Z.orig |
| # 20:43:13 | y_morin | 4) patch gcc-X.Y.Z |
| # 20:43:17 | y_morin | 5) rebuild |
| # 20:43:59 | y_morin | 6) when you are satisfied with the patching, diff against .orig to keep your patch, and add that patch to gcc's patches/gcc/X.Y.Z |
| # 20:44:26 | y_morin | 7) rm -rf ,build/src/gcc-X.Y.Z, and go back to 3) |
| # 20:44:37 | y_morin | aaribaud: of course, YMMV, as they say. |
| # 20:46:28 | aaribaud | y_morin: thanks for the detailed suggestion! That'll save me a lot of time. I'll be sure to drop you a note once I get the patch accepted by the GCC people. :) |
| # 20:46:57 | y_morin | aaribaud: what does that mean, you being the "U-Boot ARM custodian" ? |
| # 20:47:11 | aaribaud | y_morin: do you know U-Boot? |
| # 20:47:15 | y_morin | Yep. |
| # 20:47:39 | y_morin | It's the "custodian" part I don't understand (I know the word, though). |
| # 20:48:06 | y_morin | Does that mean you're considered "maintainer" for the ARM port(s) ? |
| # 20:48:08 | aaribaud | ok, simplest explanation : http://www.denx.de/wiki/U-Boot/Custodians |
| # 20:48:46 | aaribaud | you can consider me the maintainer for ARM, but in U-Boot parlance, "maintainer" is for boards. |
| # 20:48:58 | y_morin | aaribaud: OK, you're in maintainership |
| # 20:49:05 | y_morin | OK! |
| # 20:50:04 | y_morin | aaribaud: In case you need more assistance in using ct-ng, just pop here, although I'm not always on-line (I'm here ~17:00 UTC to ~22:00 UTC) |
| # 20:50:28 | y_morin | (That is off-work times in France... |
| # 20:51:26 | aaribaud | y_morin: thanks. I'd dutifully read the ct-ng info before popping in here. :) |
| # 20:51:52 | y_morin | aaribaud: :-) |
| # 20:52:16 | y_morin | aaribaud: there's some usefull stuff in docs/ but the internals are not clearly documented... :-( |
| # 20:54:02 | aaribaud | y_morin: I'll certainly be sticking to the recipe you gave me, at least for the moment. After all, I'm going to dive into the GCC internals, which is enough to keep me busy with. :) |
| # 20:54:30 | y_morin | aaribaud: that's for sure, indeed! :-) |
| # 22:17:45 | sh4rm4 | quits : Remote host closed the connection |
| # 22:19:32 | sh4rm4 | joins #crosstool-ng |
| # 23:18:36 | y_morin | quits : Quit: Nighty Night! |