cross compile
i used this toolchain
configure command: vim_cv_toupper_broken="set" vim_cv_terminfo="set" ./configure --host=arm-apple-darwin11 --with-tlib=ncurses
normal build
wasnt sure where to go for support so if theres a better place like a discord or something lmk
9.0.0618
arch linux under wsl on windows 11
windows terminal
$TERM=xterm-256color
zsh 5.9
No response
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
What's the contents of the file ./src/auto/config.log?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Issue #2058 seems similar.
Does replacing --with-tlib=ncurses with --with-tlib=tinfo help?
I found the same issue when compile the vim as well. Here is my solution:
--with-tlib=ncurses should replace by --with-tlib=tinfo . libtinfo was generated from ncurses when you add the --with-termlib whilecompiling ncurse
Alternatively, does setting vim_cv_tgetent to zero help?
vim_cv_tgetent=zero
I have experienced the same issue while building Vim 8.1 through Yocto/OE recipe as well as for Buildroot. The solution was to add:
vim_cv_tgetent=zero
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Closed #11246 as completed.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
vim_cv_tgetent=zero worked
the final configure command was:
vim_cv_memcpy_handles_overlap=set vim_cv_bcopy_handles_overlap=set vim_cv_memmove_handles_overlap=set vim_cv_stat_ignores_slash=set vim_cv_timer_create=set vim_cv_getcwd_broken=set vim_cv_toupper_broken="set" vim_cv_terminfo="set" vim_cv_tgetent=zero ./configure --host=arm-apple-darwin11 --with-tlib=ncurses
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()