Re: [vim/vim] Build error on Solaris 10 (Issue #18706)

8 views
Skip to first unread message

Christian Brabandt

unread,
Nov 9, 2025, 1:51:02 PM (2 days ago) Nov 9
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#18706)

That is a strange error, because parse_cs_f_keys() is far away from line 7753 and does not contain anything alignment specific.

With the help of chatgpt I narrowed this down to the use of the ansi_table. If this is true, does it compile, if you disable the terminal (e.g. ./configure --disable-terminal)? If yes, can you please try the following patch:

sparc_ansi_term.patch


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18706/3508676793@github.com>

idgn23

unread,
Nov 9, 2025, 2:39:25 PM (2 days ago) Nov 9
to vim/vim, Subscribed
idgn23 left a comment (vim/vim#18706)

I am still getting the same error with --disable-terminal .


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18706/3508742507@github.com>

Christian Brabandt

unread,
Nov 9, 2025, 2:48:42 PM (2 days ago) Nov 9
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#18706)

So if you remove the whole block here:
https://github.com/vim/vim/blob/aa9862a5b0e68581b07197f9c21b1441ab62a290/src/term.c#L7602-L7704

It still fails? Well, then can you bisect which patch causes the failure?


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18706/3508759610@github.com>

idgn23

unread,
11:19 AM (10 hours ago) 11:19 AM
to vim/vim, Subscribed
idgn23 left a comment (vim/vim#18706)

It was still failing.

I have verified which version is the latest one that compiles without errors. It is 9.1.1735.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18706/3517689260@github.com>

Christian Brabandt

unread,
12:07 PM (9 hours ago) 12:07 PM
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#18706)

So patch 9.1.1736 causes this which adds the parse_csi_f_keys() function. But I don't understand the error message, so not sure how to fix it.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18706/3517919157@github.com>

Christian Brabandt

unread,
12:33 PM (9 hours ago) 12:33 PM
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#18706)

Have you tried a different compiler?


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18706/3518010624@github.com>

Christian Brabandt

unread,
12:35 PM (9 hours ago) 12:35 PM
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#18706)

Oh and just a wild guess, does this help?

diff --git a/src/term.c b/src/term.c
index 4c365b19b..c317ca601 100644
--- a/src/term.c
+++ b/src/term.c
@@ -5362,7 +5362,7 @@ put_key_modifiers_in_typebuf(
     static int
 parse_csi_f_keys(int arg)
 {
-    char_u key_name[2] = "";
+    char_u key_name[2] = { 0, 0 };

     switch (arg)
     {


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18706/3518018083@github.com>

idgn23

unread,
1:36 PM (8 hours ago) 1:36 PM
to vim/vim, Subscribed
idgn23 left a comment (vim/vim#18706)

Yes, this fixes it!


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18706/3518279170@github.com>

Reply all
Reply to author
Forward
0 new messages