| # 02:06:23 | luc4 | quits : Quit: luc4 |
| # 03:10:21 | enunes | quits : Ping timeout: 276 seconds |
| # 03:12:41 | enunes | joins #crosstool-ng |
| # 09:26:23 | diorcety | joins #crosstool-ng |
| # 09:31:25 | diorcety1 | joins #crosstool-ng |
| # 09:34:03 | diorcety | quits : Ping timeout: 268 seconds |
| # 11:21:36 | blueness | quits : Quit: blueness |
| # 11:23:38 | blueness | joins #crosstool-ng |
| # 11:28:12 | blueness | quits : Client Quit |
| # 11:30:23 | blueness | joins #crosstool-ng |
| # 11:37:27 | blueness | quits : Quit: blueness |
| # 11:38:42 | blueness | joins #crosstool-ng |
| # 14:13:34 | y_morin | joins #crosstool-ng |
| # 14:51:55 | luc4 | joins #crosstool-ng |
| # 16:21:51 | blueness | quits : Quit: blueness |
| # 17:09:00 | dsmith-work | enunes: How is CT_INSTALL_DIR different or used differently than CT_PREFIX_DIR ? |
| # 17:21:24 | enunes | dsmith-work: you can't change CT_INSTALL_DIR in ct-ng menuconfig, I see that it appears in the .config (which should not be edited directly) but apparently CT_INSTALL_DIR is computed automatically |
| # 17:21:58 | aneyman | dsmith-work: AFAIU, this is a remnant of the past where you install the built toolchain to CT_INSTALL_DIR to package it but the resulting toolchain is compiled to work when installed in CT_PREFIX_DIR |
| # 17:22:39 | aneyman | but as far as I understand, it is supposed to be relocatable now, which is (probably) why CT_INSTALL_DIR is hardwired to CT_PREFIX_DIR in config/paths.in |
| # 17:22:42 | dsmith-work | Yes, that's kind of what I was hoping. |
| # 17:23:23 | dsmith-work | I don't much like that as it builds it is actually installing at the same time. |
| # 17:23:43 | aneyman | but I haven't tested the relocatability myself and I do see some CT_PREFIX_DIR paths in various places of the built toolchain (such as ld search paths, etc.) |
| # 17:23:57 | aneyman | this might be incomplete and needs more testing/cleanups, probably |
| # 17:24:14 | dsmith-work | I did try today. |
| # 17:25:07 | dsmith-work | I was able to build with a PREFIX dir with $(pwd) in it, and was able to tar that up and unpack it in /opt |
| # 17:25:45 | enunes | I have toolchains which were built in /opt and packaged in a tar, which are then downloaded and extracted directly inside a Buildroot tree and they work fine from there |
| # 17:25:57 | dsmith-work | Ok. cool |
| # 18:37:42 | blueness | joins #crosstool-ng |
| # 20:10:45 | stefanct | quits : Quit: quit |
| # 20:12:40 | stefanct | joins #crosstool-ng |
| # 20:30:41 | diorcety1 | quits : Read error: Connection reset by peer |
| # 20:56:28 | y_morin | quits : Quit: Nighty Night! |
| # 21:19:47 | anjo2 | joins #crosstool-ng |
| # 22:20:07 | anjo2 | quits : Quit: Angel Script v1.0 em www.anjo2.com |
| # 22:23:16 | luc4 | quits : Ping timeout: 264 seconds |
| # 22:27:46 | luc4 | joins #crosstool-ng |