"Dale" <rdalek1...@gmail.com>, 06.05.2019, 14:38:
> Well, trying that was worth a shot anyway. Sometimes it does fix some
> problems, although it might still be a bug. However, in this case, I
> don't think anything really changed. It looks like the same error
> again. I copied, going backwards, from the error 1, first mention of
> it, and then went back up about 70 lines or so. One may want to read it
> from bottom to top. Honestly, I can't see that anything failed but
> something seems to have failed, somewhere. Here is the error while
> running with -j1:
I got curious, so I tried to emerge guile-gtk, too.
After the ebuild failed, the output got dumped to the terminal
and showed lots of magenta warnings and cyan notes
and somewhere in there three red blobs appear:
In file included from /usr/include/guile/2.2/libguile.h:31,
from
/var/tmp/portage/x11-libs/guile-gtk-2.1-r3/work/guile-gtk-2.1/gtk-glue.c:4:
/var/tmp/portage/x11-libs/guile-gtk-2.1-r3/work/guile-gtk-2.1/gtk-glue.c: In
function ‘sgtk_gtk_input_add_full’:
/var/tmp/portage/x11-libs/guile-gtk-2.1-r3/work/guile-gtk-2.1/gtk-glue.c:3579:63:
error: ‘scm_tc16_fport’ undeclared (first use in this function); did you mean
‘scm_t_fport’?
SCM_ASSERT ((SCM_NIMP (p_source) && SCM_TYP16 (p_source) == scm_tc16_fport
&& SCM_OPPORTP (p_source)), p_source, SCM_ARG1, s_gtk_input_add_full);
^~~~~~~~~~~~~~
namely: "error", "scm_tc16_fport" and the accompanying wiggles right below.
So, as Jack correctly claimed, the problem appears in gtk-glue.c.
While I don't have a clue how to fix what is really wrong here,
I just wanted to point out that the colorful output of gcc is very helpful,
if you get to see it.
s.
