1 |
"Dale" <rdalek1967@×××××.com>, 06.05.2019, 14:38: |
2 |
|
3 |
> Well, trying that was worth a shot anyway. Sometimes it does fix some |
4 |
> problems, although it might still be a bug. However, in this case, I |
5 |
> don't think anything really changed. It looks like the same error |
6 |
> again. I copied, going backwards, from the error 1, first mention of |
7 |
> it, and then went back up about 70 lines or so. One may want to read it |
8 |
> from bottom to top. Honestly, I can't see that anything failed but |
9 |
> something seems to have failed, somewhere. Here is the error while |
10 |
> running with -j1: |
11 |
|
12 |
I got curious, so I tried to emerge guile-gtk, too. |
13 |
|
14 |
After the ebuild failed, the output got dumped to the terminal |
15 |
and showed lots of magenta warnings and cyan notes |
16 |
and somewhere in there three red blobs appear: |
17 |
|
18 |
In file included from /usr/include/guile/2.2/libguile.h:31, |
19 |
from /var/tmp/portage/x11-libs/guile-gtk-2.1-r3/work/guile-gtk-2.1/gtk-glue.c:4: |
20 |
/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’: |
21 |
/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’? |
22 |
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); |
23 |
^~~~~~~~~~~~~~ |
24 |
|
25 |
namely: "error", "scm_tc16_fport" and the accompanying wiggles right below. |
26 |
|
27 |
So, as Jack correctly claimed, the problem appears in gtk-glue.c. |
28 |
|
29 |
While I don't have a clue how to fix what is really wrong here, |
30 |
I just wanted to point out that the colorful output of gcc is very helpful, |
31 |
if you get to see it. |
32 |
|
33 |
s. |