ibotlog2html for #crosstool-ng

<< Previous 2013-05-28 Next >>

# 00:19:45 Skindred quits : Ping timeout: 248 seconds
# 00:21:10 huhlig-home quits : Ping timeout: 256 seconds
# 00:41:01 AvengerMoJo joins #crosstool-ng
# 01:27:55 blueness|uclibc joins #crosstool-ng
# 01:27:55 blueness|uclibc quits : Changing host
# 01:27:55 blueness|uclibc joins #crosstool-ng
# 01:47:47 huhlig-home joins #crosstool-ng
# 02:19:43 aalv quits : Read error: Connection reset by peer
# 02:19:49 aalv1 joins #crosstool-ng
# 02:25:37 AvengerMoJo quits : Quit: AvengerMoJo
# 02:42:15 blueness|uclibc quits : Remote host closed the connection
# 03:18:17 AvengerMoJo joins #crosstool-ng
# 04:01:31 alan_o joins #crosstool-ng
# 04:02:12 alan_o quits : Client Quit
# 04:02:26 alan_o joins #crosstool-ng
# 04:24:49 alan_o quits : Remote host closed the connection
# 06:19:16 smartin quits : Quit: brb
# 06:21:52 huhlig-home quits : Ping timeout: 256 seconds
# 06:23:27 smartin joins #crosstool-ng
# 06:26:38 y_morin joins #crosstool-ng
# 06:32:30 AvengerMoJo quits : Quit: AvengerMoJo
# 07:19:23 jmm quits : Ping timeout: 260 seconds
# 07:19:34 jmm joins #crosstool-ng
# 07:25:14 Skindred joins #crosstool-ng
# 09:27:13 Net147 joins #crosstool-ng
# 09:56:01 AvengerMoJo joins #crosstool-ng
# 12:08:42 Skindred quits : Remote host closed the connection
# 12:30:04 AvengerMoJo quits : Quit: AvengerMoJo
# 12:55:44 idallasj quits : Read error: Connection reset by peer
# 12:56:09 idallasj1 joins #crosstool-ng
# 13:59:46 AvengerMoJo joins #crosstool-ng
# 14:17:20 AvengerMoJo quits : Write error: Connection reset by peer
# 14:17:52 crazedpsyc quits : Ping timeout: 249 seconds
# 14:18:02 AvengerMoJo_ joins #crosstool-ng
# 14:18:02 AvengerMoJo_ is now known as: AvengerMoJo
# 14:18:14 crazed- joins #crosstool-ng
# 14:20:07 crazed- is now known as: crazedpsyc
# 14:31:42 huhlig-home joins #crosstool-ng
# 14:40:43 aalv1 quits : Ping timeout: 264 seconds
# 14:44:03 aalv joins #crosstool-ng
# 14:47:02 huhlig-home quits : Ping timeout: 256 seconds
# 14:52:04 jevin quits : Quit: Textual IRC Client: www.textualapp.com
# 14:58:31 jevin joins #crosstool-ng
# 15:43:19 shawnjgoff The LIBC_LOCALES option for glibc has a big warning, but it's not there for eglibc. Is the warning not waranted for eglibc, or should it really be there?
# 15:52:32 Net147 quits : Quit: HydraIRC -> http://www.hydrairc.com <- Nine out of ten l33t h4x0rz prefer it
# 16:16:01 y_morin shawnjgoff: the warning about endianness and bitness? Not needed for eglibc, as it does the correct thing.
# 16:24:34 Thomas1 joins #crosstool-ng
# 16:35:12 shawnjgoff Awesome. Thanks, y_morin
# 16:51:48 diorcety joins #crosstool-ng
# 17:43:14 plfiorini joins #crosstool-ng
# 19:23:45 plfiorini quits : Ping timeout: 248 seconds
# 19:26:01 huhlig-home joins #crosstool-ng
# 19:26:57 codyps quits : Ping timeout: 252 seconds
# 19:28:48 smartin_ joins #crosstool-ng
# 20:10:55 Thomas1 quits : Quit: Thomas1
# 20:55:55 shawnjgoff I have a crosstool_ng error: "scripts/functions: line 201: printf: write error: Input/output error".
# 20:56:28 shawnjgoff At first I thought maybe the fd &6 wasn't defined, but when that happens, the shell actually tells you the fd is not defined (in bash and dash, at least).
# 20:57:24 shawnjgoff Doh, no I typed bash both times instead of dash. I don't have dash installed, so it's not an error from dash.
# 20:59:31 codyps joins #crosstool-ng
# 21:01:50 shawnjgoff And apparently someone else has had this problem, too: http://crosstool-ng.org/download/ibot-logs/2013-05-03.html
# 21:16:56 jevin quits : Ping timeout: 252 seconds
# 21:24:18 jevin_ joins #crosstool-ng
# 21:30:12 jevin_ quits : Ping timeout: 252 seconds
# 21:37:01 y_morin shawnjgoff: can you run: ulimit -n
# 21:38:23 blueness|uclibc joins #crosstool-ng
# 21:38:23 blueness|uclibc quits : Changing host
# 21:38:23 blueness|uclibc joins #crosstool-ng
# 21:43:48 AvengerMoJo_ joins #crosstool-ng
# 21:44:10 AvengerMoJo quits : Ping timeout: 252 seconds
# 21:44:11 AvengerMoJo_ is now known as: AvengerMoJo
# 21:49:23 smartin_ quits : Quit: leaving
# 21:55:41 plfiorini joins #crosstool-ng
# 22:04:35 AvengerMoJo quits : Quit: AvengerMoJo
# 22:21:38 shawnjgoff y_morin: ulimit -n gives 1024
# 22:22:10 y_morin shawnjgoff: Hm,, so not a limit on file descriptors. Does it happen at the beginning of the build? Or much later?
# 22:22:14 shawnjgoff I just ran ct-ng build again without changing anything and it got past that part.
# 22:23:07 shawnjgoff y_morin: I'm not sure - it happened once.
# 22:24:26 y_morin shawnjgoff: Enough space on disk? :-/
# 22:24:59 shawnjgoff y_morin: plenty of space, plenty of inodes
# 22:25:16 y_morin shawnjgoff: just eliminating the obvious. ;-)
# 22:25:26 shawnjgoff Yeah.
# 22:25:32 y_morin shawnjgoff: Well, no clue. I never ever saw it...
# 22:25:46 shawnjgoff Okay. If it comes up again, I'll remember to save the log and config.
# 22:26:08 y_morin shawnjgoff: Was there already some messages on screen, or none at all?
# 22:26:28 y_morin shawnjgoff: Because if you already had ct-ng messages, that's stange...
# 22:27:18 shawnjgoff There were a lot of messages. It had been going for several minutes.
# 22:27:52 y_morin shawnjgoff: OK, so bash had an issue using an already oppened file descriptor...
# 22:28:15 y_morin shawnjgoff: did you have other stuff running in parallel (eg. another build, or something that may be fd-hungry) ?
# 22:28:47 shawnjgoff No, in fact, I have to close everything down when I do a ct-ng build because cloog/ppl sucks up all the memory and fails if it can't get enough.
# 22:29:58 shawnjgoff Maybe other threads of the build are fd-heavy?
# 22:31:18 y_morin shawnjgoff: Well, not really. Depending on the number of CPUs you have, you can count in the order of 5-10 fds per CPUs
# 22:31:56 y_morin shawnjgoff: which, unless you have like 100 CPUs, you're well.
# 22:33:15 shawnjgoff Yeah, that's not it.
# 23:01:38 y_morin quits : Quit: Nighty Night!

Generated by ibotlog2html by Yann E. MORIN