| # 00:37:36 | kos_tom | quits : Ping timeout: 265 seconds |
| # 00:39:05 | esbenh | quits : *.net *.split |
| # 00:39:06 | sh[4]rm4 | quits : *.net *.split |
| # 00:39:10 | mnt_real | quits : *.net *.split |
| # 00:39:15 | mpee | quits : *.net *.split |
| # 00:39:15 | ben1066_ | quits : *.net *.split |
| # 00:39:17 | ChanServ | quits : *.net *.split |
| # 00:44:11 | kos_tom_ | joins #crosstool-ng |
| # 00:44:11 | mpee | joins #crosstool-ng |
| # 00:44:11 | ben1066_ | joins #crosstool-ng |
| # 00:44:11 | sh[4]rm4 | joins #crosstool-ng |
| # 00:44:11 | mnt_real | joins #crosstool-ng |
| # 00:44:11 | esbenh | joins #crosstool-ng |
| # 00:44:11 | ChanServ | joins #crosstool-ng |
| # 01:59:40 | imMute | mpee: talk to y_morin when he's around |
| # 01:59:50 | mpee | imMute: thanks |
| # 04:46:30 | mpee | quits : Read error: Connection reset by peer |
| # 04:47:07 | mpee | joins #crosstool-ng |
| # 05:45:32 | hgb | joins #crosstool-ng |
| # 05:45:54 | hgb | Hi. I'm trying to build a powerpc toolchain with crosstool-ng, and I get this error: |
| # 05:45:57 | hgb | [ERROR] checking dynamic linker characteristics... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES. |
| # 05:46:15 | hgb | It's a pretty recent ct-ng (hg+default-c800b7d6a50c) |
| # 05:46:33 | hgb | I build it with static linking (of the host tools= |
| # 05:46:35 | hgb | ) |
| # 05:46:53 | hgb | gcc-4.7.0, glibc-2.13, binutils-2.22, linux-3.0.30 |
| # 05:46:57 | hgb | Anyone seen this? |
| # 05:47:07 | hgb | I've seen it a bit on google, but very old posts. |
| # 06:30:42 | mpee | hgb: sorry no idea about your error, I have a working powerpc config with slightly older components |
| # 06:40:34 | hgb | mpee: Do you build it statically? |
| # 06:40:46 | mpee | no |
| # 06:43:27 | hgb | Hm |
| # 06:48:11 | mpee | hgb: I haven't tried, do you think that's part of your problem? |
| # 06:54:42 | hgb | mpee: Maybe. I used to build them dynamically linked, but that's a bit of a hassle when our hosts change, and also I like to be able to build on my work station, which is F16, while the build servers are CentOS6, so it's useful to do static linking. |
| # 06:54:52 | hgb | mpee: I've built arm toolchains, though, and they work. |
| # 06:55:01 | hgb | So it certainly doesn't have to be the problem. |
| # 06:55:18 | mpee | hgb: ok, I'm just trying a static build here - gcc 4.6 based though |
| # 07:07:44 | hgb | mpee: Seem to recall I tried a 4.6.3-based on as well, failing in the same way |
| # 07:17:19 | mpee | hgb: seems to have worked, gcc 4.6.2, binutils 2.20.1a, glibc 2.13 |
| # 07:26:23 | hgb | Hmm |
| # 07:27:04 | hgb | mpee: http://fpaste.org/woLF/ <- my .config. Can you pastebin yours somewhere? |
| # 07:29:36 | mpee | hgb: http://fpaste.org/stz8/ |
| # 07:32:48 | mpee | ah, mine is 64 bit, yours is 32, so YMMV :) |
| # 07:37:00 | hgb | Yeah, I noticed. Not much else different, though, except the version numbers. |
| # 07:53:04 | mpee | quits : Quit: Leaving. |
| # 08:18:57 | smartin | joins #crosstool-ng |
| # 09:16:03 | al` | quits : Read error: Connection reset by peer |
| # 09:16:13 | al` | joins #crosstool-ng |
| # 13:15:51 | smartin | quits : Ping timeout: 245 seconds |
| # 13:28:46 | smartin | joins #crosstool-ng |
| # 14:54:52 | sh[4]rm4 | quits : Ping timeout: 276 seconds |
| # 15:03:32 | sh[4]rm4 | joins #crosstool-ng |
| # 15:29:46 | smartin | quits |
| # 17:02:11 | smartin | joins #crosstool-ng |
| # 18:39:49 | smartin | is now known as: smartin|away |
| # 20:05:01 | smartin|away | quits |
| # 20:45:12 | y_morin | joins #crosstool-ng |
| # 20:45:12 | y_morin | quits : Client Quit |