|
From: | Gábor Boskovits |
Subject: | bug#29537: Core updates broken |
Date: | Sun, 3 Dec 2017 09:41:36 +0100 |
It seems, that we have a breakage in current core-updates. m4, gettext, and at least a few other packages fail to build.We had a discussion about that on irc, here are the important points:
[09:34:53] * g_bor has joined #guix [09:34:58] <g_bor> [09:37:37] <g_bor> [09:38:03] <g_bor> [09:38:10] <g_bor>
[16:46:05] <civodul> [16:46:16] <civodul> [16:47:16] <mb[m]1> [16:47:24] * kristofer has joined #guix [16:53:03] <civodul> [16:54:11] <mb[m]1> [16:54:35] <civodul> [16:54:41] <civodul> [16:54:46] <mb[m]1> [16:55:27] * jonsger has joined #guix [16:55:31] <mb[m]1> [16:55:36] <civodul> [16:55:41] <mb[m]1> [16:56:24] <civodul> [16:56:28] <civodul>
[16:57:52] <mb[m]1> [16:57:56] * jonsger has joined #guix [17:00:55] <mb[m]1> [17:00:57] <mb[m]1> [17:01:24] <civodul> [17:06:59] * ryanwatkins has joined #guix [17:11:08] <g_bor> [17:11:18] <g_bor> [17:11:30] <g_bor> [17:11:51] <g_bor> [17:13:38] <civodul> [17:13:45] <mb[m]1> [17:14:36] <g_bor> [17:14:55] <g_bor> [17:15:05] <g_bor> [17:16:04] * civodul has quit (Read error: Connection reset by peer) [17:17:26] <g_bor> [17:18:19] * civodul has joined #guix [17:18:42] <mb[m]1> [17:19:17] <g_bor> [17:19:38] <g_bor> [17:20:08] <g_bor> [17:20:15] <g_bor> [17:22:51] <g_bor> [17:23:01] <g_bor> [17:26:26] * xkapastel has joined #guix [17:30:38] <mb[m]1> [17:31:12] <g_bor> [17:31:21] <g_bor> [17:32:01] <mb[m]1> [17:32:24] <g_bor>
[17:36:36] <g_bor> [17:36:58] <g_bor> [17:37:13] <g_bor> g_bor> Ok, now it's building.<g_bor> I think this will take a time...<g_bor> (guile does take some time :) )<g_bor> I'm trying to help to switch the default icedtea to icedtea-8, and we'd like to that on core-updates...<g_bor> I've just written on the mailing list, that it would be nice if we could have substitutes for the core-updates gnu-build-system.<g_bor> That could speed things like this up.<efraim> mb[m]1: just popped in for a second, core-updates is failing on aarch64 also<efraim> civodul too ^<g_bor> Oh, well.<g_bor> Do we have a bug report on that already?<g_bor> Now I'm trying what mb[m]1 suggested, by reverting the ncurses commit.<g_bor> It might be easier to track related information in a bug...<<g_bor> reverting 667082d59104d4b964dce878f5e8c0f8ad1be958 did not help Does anyone know of a last working commit id?I'm trying to seen if it's working after last merge of master, but if someone knows a later point to start investigating the issue would help.It would also help, if someone with a more powerful computer could help, as building on mine is very slow.
[Prev in Thread] | Current Thread | [Next in Thread] |