| # 00:03:48 | bhundven | joins #crosstool-ng |
| # 01:18:54 | tzanth | joins #crosstool-ng |
| # 01:19:49 | tzarc | quits : Ping timeout: 260 seconds |
| # 03:33:12 | bhundven | quits : Ping timeout: 252 seconds |
| # 03:42:42 | bhundven | joins #crosstool-ng |
| # 03:42:42 | bhundven | quits : Changing host |
| # 03:42:42 | bhundven | joins #crosstool-ng |
| # 03:54:20 | mnt_real_ | quits : Quit: Ex-Chat |
| # 04:48:18 | alan_o | quits : Remote host closed the connection |
| # 05:21:25 | esbenh | quits : *.net *.split |
| # 05:21:25 | sh4rm4 | quits : *.net *.split |
| # 05:21:27 | tzanth | quits : *.net *.split |
| # 05:21:28 | ccole | quits : *.net *.split |
| # 05:21:30 | ChanServ | quits : *.net *.split |
| # 05:22:05 | tzanth | joins #crosstool-ng |
| # 05:22:05 | sh4rm4 | joins #crosstool-ng |
| # 05:22:05 | ccole | joins #crosstool-ng |
| # 05:22:05 | esbenh | joins #crosstool-ng |
| # 05:22:05 | ChanServ | joins #crosstool-ng |
| # 06:18:03 | bhundven | quits : Quit: Leaving. |
| # 09:09:51 | esbenh | quits : *.net *.split |
| # 09:26:28 | smartin | joins #crosstool-ng |
| # 09:32:56 | smartin | quits : Ping timeout: 245 seconds |
| # 09:58:20 | esbenh | joins #crosstool-ng |
| # 10:01:01 | y_morin | joins #crosstool-ng |
| # 10:19:21 | tzanth | quits : Read error: Connection reset by peer |
| # 10:21:46 | tzarc | joins #crosstool-ng |
| # 11:27:50 | beneth` | quits : Ping timeout: 272 seconds |
| # 11:28:20 | beneth` | joins #crosstool-ng |
| # 11:49:31 | kos_tom | quits : Quit: leaving |
| # 11:56:57 | kos_tom | joins #crosstool-ng |
| # 12:02:08 | kos_tom | quits : Ping timeout: 240 seconds |
| # 12:08:53 | kos_tom | joins #crosstool-ng |
| # 12:12:22 | kos_tom_ | joins #crosstool-ng |
| # 13:15:28 | kos_tom_ | quits : Quit: leaving |
| # 16:12:54 | kos_tom | y_morin: hello. |
| # 16:13:02 | kos_tom | y_morin: is it normal that on failures, the build doesn't stop? |
| # 16:13:41 | kos_tom | y_morin: see for example http://code.bulix.org/4vorlq-81470?raw |
| # 16:25:57 | y_morin | kos_tom: nope, it's not. |
| # 16:26:09 | y_morin | I'm investigating that, too... |
| # 16:27:09 | y_morin | kos_tom: http://crosstool-ng.org/download/ibot-logs/2012-05-05.html#quick-21:42:52 |
| # 16:28:32 | y_morin | But it seems it depends on the type of failure, and where it happens, because I already provoked four failures here, and they all got caught properly... :-( |
| # 16:29:14 | y_morin | kos_tom: BTW, I also have a fix for the gcc-4.7's GCC_NO_EXECUTABLES |
| # 16:29:30 | y_morin | Still investigating, but seems it is working, now... |
| # 16:38:24 | y_morin | kos_tom: still running on your lenny system? |
| # 16:38:47 | y_morin | Because there is a change in how bash-4 sets its internal variables |
| # 16:39:08 | y_morin | And as I'm on squeeze, I don't see the issue. |
| # 16:39:25 | y_morin | That's probably why a failure is not properly caught... |
| # 16:49:40 | kos_tom | y_morin: yes, I'm still running on my lenny system. |
| # 17:45:45 | kos_tom | y_morin: it doesn't make things easy to find which toolchain was built successfully, which toolchain wasn't |
| # 18:07:23 | joko | quits : Read error: Connection reset by peer |
| # 18:20:31 | kos_tom | and now: |
| # 18:20:33 | kos_tom | [ERROR] /home/test/crosstool-ng-1.15.0/.build/src/gcc-4.6.3/libgcc/config/libbid/bid_decimal_globals.c:47:18: fatal error: fenv.h: No such file or directory |
| # 18:52:13 | y_morin | kos_tom: Yep, I understand. Fact is, nothing changed in this respect between 1.14 and 1.15... |
| # 18:53:51 | y_morin | kos_tom: were you still using pre-1.14.0 before switching to 1.15.0? |
| # 18:59:01 | kos_tom | I think on this machine, I switched from 1.13.x to 1.15 directly |
| # 19:00:41 | y_morin | kos_tom: OK, I see why you get the issue only now. |
| # 19:01:32 | y_morin | kos_tom: but as you saif earlier, does it make sense maintaining backward compatibility with lenny, which is no longer maintained? |
| # 19:01:36 | y_morin | *said |
| # 19:11:07 | kos_tom | y_morin: probably not. |
| # 19:11:24 | kos_tom | do you have an idea for the fenv.h problem? |
| # 19:12:15 | y_morin | kos_tom: not on the top of my hat, but it rings a bell... |
| # 19:13:15 | y_morin | kos_tom: I am trying to get 1.15 in shape for inclusion in BR, so I think your breakage issue not being caught is important to fix, in fact. |
| # 19:13:42 | y_morin | kos_tom: probably, a lot of people, especially in companies, are still using 'legacy' distros... |
| # 19:14:03 | y_morin | So if the fix is simple enough, I'll add it. |
| # 19:16:10 | y_morin | kos_tom: the problem is identified and fixed, now. It is a limitation in POSIX, and that bash decided to interpret, and gets right (for once!). |
| # 19:17:00 | y_morin | BTW, any idea if "IEEE Std 1003.1" has a more recent issue than 2008 ? |
| # 19:18:37 | y_morin | Well, issue 7 was in 2008, issue 6 was in 2004. Maybe we'll get issue 8 this year! :-] |
| # 19:21:52 | y_morin | kos_tom: could you try this patch: http://code.bulix.org/zdqf5f-81472 |
| # 19:25:16 | y_morin | Well POSIX does not say whether "set -e" should catch a sub-shell that exits with !0. bash-3 did not catch it, while bash-4 does. |
| # 19:25:58 | y_morin | Well, the patch catches errors in my lenny-32 chroot. |
| # 19:26:19 | y_morin | kos_tom: does it work for you? |
| # 20:19:41 | kos_tom | sorry, I was having dinner; |
| # 20:20:02 | y_morin | kos_tom: No problem! ;-) |
| # 20:20:17 | kos_tom | I'll watch a movie now, I'll test this later (tomorrow probably) |
| # 20:20:50 | y_morin | It's difficult to tell whether you're on-line or not, your status almost never goes to "away". ;-) |
| # 20:21:01 | y_morin | OK, happy evening! |
| # 21:15:41 | y_morin | GAhhh! I pushed a bad changeset... :-( |
| # 21:15:47 | y_morin | And released it! |
| # 21:15:50 | y_morin | AHHH!!!! |
| # 21:15:57 | sh4rm4 | :/ |
| # 21:16:19 | sh4rm4 | time for a bugfix release... |
| # 21:20:28 | y_morin | Yep, a bug-fix over a bug-fix... |
| # 23:01:41 | y_morin | quits : Quit: Night! |