| # 00:16:32 | HanSooloo | joins #crosstool-ng |
| # 02:56:50 | cody1 | joins #crosstool-ng |
| # 03:30:16 | bhundven|afk | is now known as: bhundven |
| # 04:29:46 | cody1 | quits : Quit: Leaving. |
| # 08:04:41 | smartin | joins #crosstool-ng |
| # 09:54:52 | bhundven | is now known as: bhundven|afk |
| # 12:54:47 | smartin | quits : Ping timeout: 246 seconds |
| # 12:57:55 | smartin | joins #crosstool-ng |
| # 13:08:07 | smartin | quits : Ping timeout: 240 seconds |
| # 13:08:35 | smartin | joins #crosstool-ng |
| # 13:38:35 | alan_o | joins #crosstool-ng |
| # 14:16:18 | HanSooloo | quits : Quit: HanSooloo |
| # 14:16:46 | HanSooloo | joins #crosstool-ng |
| # 16:41:48 | cody1 | joins #crosstool-ng |
| # 17:02:37 | HanSooloo | quits : Quit: HanSooloo |
| # 17:03:09 | HanSooloo | joins #crosstool-ng |
| # 17:41:37 | cody1 | quits : Quit: Leaving. |
| # 17:44:46 | cody1 | joins #crosstool-ng |
| # 18:07:26 | pnoffke | Hi. I built a cross-compiler (x86_64), and now I'm trying to build the Linux kernel. Is there any reason that HOSTCC should use the cross-compiler? I think this is only for doing the menuconfig stuff. Is that correct? |
| # 18:11:11 | bhundven|afk | is now known as: bhundven |
| # 18:24:21 | cody1 | pnoffke: yes, that is correct. |
| # 18:24:51 | pnoffke | Thanks, cody1. |
| # 18:34:31 | pnoffke | I've got crosstool's versions of gcc, g++, etc. on my path before the host's gcc path, and these are getting used as HOSTCC. Why the executables without the x86_64-unknown-linux-gnu- prefix? If I try to compile even a hello world file, I get this error: |
| # 18:34:35 | pnoffke | gcc: error trying to exec 'cc1': execvp: No such file or directory |
| # 18:34:58 | pnoffke | If I take crosstool's gcc off my path, will it break something else? |
| # 18:42:57 | pnoffke | My guess is these short-named versions just exist to force you to specify the longer-named versions, but I'm not sure of the reasoning for that. |
| # 18:49:19 | sh4rm4 | quits : Remote host closed the connection |
| # 18:49:59 | sh4rm4 | joins #crosstool-ng |
| # 18:50:39 | pnoffke | (In other words, if you put it on the path, a call to gcc won't work. So you don't put it on the path, and then the call to gcc is the host's gcc. The latter case is needed for cases like the kernel. |
| # 19:01:20 | pnoffke | Okay, I think this link explains it. The short-named versions are not supposed to be on the path. |
| # 19:01:23 | pnoffke | http://permalink.gmane.org/gmane.comp.gcc.cross-compiling/10695 |
| # 19:01:26 | smartin | quits : Quit: leaving |
| # 19:10:49 | cody1 | pnoffke: yep, you should just have ${HOME}/x-tools/*/bin in your path (or whatever you changed the prefix to), not ${HOME}/x-tools/*/*/bin |
| # 19:10:57 | pnoffke | quits : Quit: leaving |
| # 19:30:05 | pnoffke | joins #crosstool-ng |
| # 20:31:32 | smartin | joins #crosstool-ng |
| # 21:10:55 | sh4rm4 | https://github.com/GregorR/musl-cross <- the "ct-ng" for musl |
| # 22:01:00 | cody1 | sh4rm4: doesn't handle canceled downloads or extracts nicely. |
| # 22:02:11 | sh4rm4 | hey, it's 2 days old |
| # 22:02:26 | sh4rm4 | anyway, you can file an issue there |
| # 22:20:18 | smartin | quits : Quit: leaving |
| # 22:55:18 | alan_o | quits : Ping timeout: 264 seconds |
| # 23:06:45 | alan_o | joins #crosstool-ng |
| # 23:48:42 | alan_o | quits : Ping timeout: 264 seconds |
| # 23:59:52 | alan_o | joins #crosstool-ng |