| # 04:07:15 | alan_o | quits : Remote host closed the connection |
| # 04:45:45 | djerome | quits : Remote host closed the connection |
| # 06:10:50 | djerome | joins #crosstool-ng |
| # 06:29:38 | djerome | quits : Remote host closed the connection |
| # 07:10:18 | dalias | quits : Ping timeout: 240 seconds |
| # 07:11:18 | dalias | joins #crosstool-ng |
| # 08:38:31 | tlwoerner | quits : Ping timeout: 245 seconds |
| # 08:52:32 | aalv | joins #crosstool-ng |
| # 10:35:33 | tlwoerner | joins #crosstool-ng |
| # 10:36:29 | aalv | quits : Remote host closed the connection |
| # 10:40:14 | aalv | joins #crosstool-ng |
| # 11:27:09 | alan_o | joins #crosstool-ng |
| # 11:57:00 | mingwandroid | joins #crosstool-ng |
| # 12:55:30 | perr | joins #crosstool-ng |
| # 12:57:01 | loide | quits : Quit: Saindo |
| # 13:37:12 | perr | quits : Ping timeout: 268 seconds |
| # 13:50:58 | perr | joins #crosstool-ng |
| # 14:47:33 | aalv | quits : Ping timeout: 265 seconds |
| # 15:02:52 | aalv | joins #crosstool-ng |
| # 15:51:18 | perr | quits : Quit: Leaving |
| # 16:45:21 | y_morin | joins #crosstool-ng |
| # 16:49:09 | Martell | joins #crosstool-ng |
| # 16:49:36 | Martell | ping y_morin |
| # 16:50:10 | Martell | Is there a way to have a seperate install dir for binutils to gcc? |
| # 16:50:22 | Martell | I can't seem to find that in the documentation |
| # 16:51:58 | y_morin | Martell: Hello. No, we have only one install dir. It's on purpose. There is no reason, in the context on ct-ng, to cater for this use-case. |
| # 16:53:24 | Martell | okay thanks y_morin. The reason I asked is because I wanted to make packages for a package manager |
| # 16:53:36 | Martell | as in gcc binutils seperate packages |
| # 16:53:51 | y_morin | Martell: The toolchain as a whole is the result. It makes no sense to byundle it into different packages. |
| # 16:53:59 | y_morin | *bundle |
| # 16:55:48 | Martell | You are correct I have one example though |
| # 16:55:59 | Martell | lets say we have gdb in there as well |
| # 16:56:27 | Martell | with having seperate packages for the package manager they not have the option of leaving gdb out if they dont need it |
| # 16:56:51 | y_morin | Martell: The cross or the native gdb? |
| # 16:56:57 | Martell | *they have the option |
| # 16:57:04 | Martell | cross |
| # 16:57:07 | Martell | i think |
| # 16:57:09 | y_morin | Martell: IMHO, the cross gdb does belong to the toolchain. |
| # 16:57:43 | y_morin | Martell: However, the native gdb (to run on the target) does not really belong to the toolchain. But you can just rip it ou, it's installed in its won debug-root. |
| # 16:58:11 | y_morin | *rip it out |
| # 16:58:19 | Martell | o wait i meant native |
| # 16:58:22 | y_morin | *own debug-root |
| # 16:58:29 | Martell | as in runs on the host |
| # 16:58:37 | Martell | and debugs a remote computer? |
| # 16:58:56 | y_morin | Martell: The cross gdb runs on the same machine as the cross gcc, ie. the host. |
| # 16:59:03 | y_morin | Martell: The native gdb runs on the target. |
| # 16:59:10 | Martell | yes thats whay i meant |
| # 16:59:16 | Martell | its a cross gdb |
| # 16:59:59 | y_morin | Martell: GTG, back later tonight... |
| # 17:01:02 | Martell | okay thanks for reply :) |
| # 17:55:51 | aalv | quits : Ping timeout: 255 seconds |
| # 17:59:21 | xrl_____ | is now known as: xrl |
| # 18:49:56 | alan_o | quits : Ping timeout: 265 seconds |
| # 19:16:55 | alan_o | joins #crosstool-ng |
| # 19:24:58 | Martell_ | joins #crosstool-ng |
| # 19:27:24 | Martell | quits : Ping timeout: 265 seconds |
| # 19:27:58 | loide | joins #crosstool-ng |
| # 19:29:34 | Martell_ | quits : Ping timeout: 265 seconds |
| # 19:32:23 | mingwandroid | quits : Remote host closed the connection |
| # 19:47:41 | djerome | joins #crosstool-ng |
| # 20:12:52 | djerome | quits : Remote host closed the connection |
| # 21:32:29 | loide | quits : Quit: Saindo |
| # 22:08:12 | djerome | joins #crosstool-ng |
| # 22:17:15 | alan_o | quits : Quit: Leaving |
| # 23:45:50 | y_morin | quits : Quit: Nighty Night! |