| # 00:20:00 | hrubi | quits : Ping timeout: 264 seconds |
| # 01:02:44 | codyps | quits : Ping timeout: 248 seconds |
| # 01:46:18 | codyps | joins #crosstool-ng |
| # 02:16:44 | diorcety | quits : Read error: Connection reset by peer |
| # 02:31:16 | codyps | quits : Ping timeout: 248 seconds |
| # 02:36:13 | codyps | joins #crosstool-ng |
| # 02:40:54 | codyps | quits : Ping timeout: 264 seconds |
| # 02:55:07 | codyps | joins #crosstool-ng |
| # 05:07:45 | alan_o | quits : Quit: Leaving |
| # 06:19:09 | plfiorini | quits : Quit: Leaving |
| # 07:06:56 | tkil | quits : Ping timeout: 252 seconds |
| # 07:14:06 | tkil | joins #crosstool-ng |
| # 07:22:00 | smartin | joins #crosstool-ng |
| # 07:34:44 | smartin | quits : Ping timeout: 248 seconds |
| # 07:37:10 | smartin | joins #crosstool-ng |
| # 09:59:48 | Net147 | joins #crosstool-ng |
| # 13:16:08 | devcoder | joins #crosstool-ng |
| # 13:21:36 | devcoder | quits : Quit: devcoder |
| # 13:38:10 | Net147 | quits : Quit: HydraIRC -> http://www.hydrairc.com <- The professional IRC Client :D |
| # 16:41:28 | TheBrayn | how can I install g++ on top of an existing toolchain |
| # 16:41:35 | TheBrayn | I don't want to build the base stuff again |
| # 16:55:07 | smartin | quits : Quit: leaving |
| # 18:03:56 | lucasrangit | joins #crosstool-ng |
| # 18:04:29 | hrubi | joins #crosstool-ng |
| # 18:05:48 | plfiorini | joins #crosstool-ng |
| # 18:08:35 | lucasrangit | I've built a x86_64 cross-compiler so that I can link in an older version of glibc (2.12.2). However, the binary I produce has multiple versions of glibc listed; one being 2.14 (my host has 2.15), 2.4, and 2.2.5. ldd on the target shows that 2.14 is not found. Any suggestions on what the problem may be and how to troubleshoot? |
| # 18:19:52 | smartin | joins #crosstool-ng |
| # 18:26:19 | codyps | quits : Quit: Leaving. |
| # 18:26:35 | codyps | joins #crosstool-ng |
| # 18:31:35 | y_morin | joins #crosstool-ng |
| # 20:21:41 | lucasrangit | How do I tell GCC to use the sysroot created by ct-ng? |
| # 20:35:34 | lucasrangit | Even after I use -nostdinc -isysroot my binary still links to multiple versions of glibc. Any ideas why this is happening? |
| # 20:36:16 | hrubi | quits : Ping timeout: 245 seconds |
| # 20:40:57 | y_morin | lucasrangit: The cross-gcc built by ct-ng will *by default* look in the sysroot created duribng the build. |
| # 20:41:52 | y_morin | lucasrangit: For example, for an arm toolchain: arm-unknown-linux-gnueabi-gcc *will* look in the associated sysroot. |
| # 20:43:38 | lucasrangit | y_morin: thanks. i think i figured out my issue.... |
| # 20:43:51 | y_morin | lucasrangit: Good!, What was it? |
| # 20:46:23 | dalias | :) |
| # 20:48:50 | hrubi | joins #crosstool-ng |
| # 20:53:40 | lucasrangit | y_morin: this is embarrassing, I'm using scons to cross-compile. and for whatever reason if I use the short names for the tool chain (gcc, g++, ar, etc...) it doesn't find cc1plus. So when I switched the bin directory to the fully qualified name (x86_64-unknown-linux-gnu-...) scons couldn't find my cross tool chain and used my hosts. |
| # 20:54:05 | y_morin | lucasrangit: 'gcc', 'g++ |
| # 20:54:13 | y_morin | Arg.. Let me do it again... |
| # 20:54:32 | lucasrangit | ;) |
| # 20:54:35 | y_morin | lucasrangit: 'gcc', 'g++'... are your native tools. |
| # 20:55:07 | y_morin | lucasrangit: your cross-compile tools are in: ${CT_PREFIX_DIR}/bin/ |
| # 20:55:29 | lucasrangit | y_morin: right, I mean the short names in '/opt/crosstool/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/bin' |
| # 20:55:46 | y_morin | lucasrangit: OH, those are internal tools! Don't use them directly! |
| # 20:55:52 | lucasrangit | y_morin: the g++ in there couldn't find cc1plus |
| # 20:56:24 | y_morin | lucasrangit: See my comment just above. |
| # 20:56:30 | y_morin | lucasrangit: And look at the doc, it's explained how to use the toolchain. ;-) |
| # 20:57:11 | lucasrangit | y_morin: I will read it again. I must not have registered the "internal" nature of those binaries |
| # 20:57:26 | y_morin | lucasrangit: It's documented in 'docs/5 - Using the toolchain.txt' in the source of crosstool-NG. ;-p |
| # 20:58:06 | lucasrangit | y_morin: thanks! i'm browsing the git repo now |
| # 20:58:12 | y_morin | reads that file again. It is not really explicit, indeed... |
| # 20:58:36 | y_morin | thinks that file (esp. the first chapter) would highly benefit from some rewording... :-/ |
| # 21:00:45 | lucasrangit | y_morin: I'll read it and try to put my suggestions in to a patch. thank you for stopping by the chat and for the great software! |
| # 21:00:57 | y_morin | lucasrangit: Also: http://crosstool-ng.org/hg/crosstool-ng/file/67df47c6ccd0/docs/3%20-%20Configuring%20a%20toolchain.txt#l57 |
| # 21:01:05 | y_morin | lucasrangit: Thanks! ;-) |
| # 21:18:46 | hrubi | quits : Ping timeout: 245 seconds |
| # 22:15:31 | smartin | quits : Quit: leaving |
| # 22:21:49 | y_morin | quits : Quit: Nighty Night! |
| # 22:37:47 | diorcety | joins #crosstool-ng |
| # 23:05:31 | lucasrangit | parts #crosstool-ng |
| # 23:53:20 | hrubi | joins #crosstool-ng |