Open Vort opened 1 day ago
In the configure script there are checks whether or not readline needs the curses library. Checks for curses variants are only present if the term gui is compiled in. For testing you could try to build with --with-term. If this helps, I can have a look how to make the readline checks work correctly.
It does not work with MSYS2.
There is clang64/mingw-w64-clang-x86_64-ncurses package, which have no .
And there is msys/ncurses-devel package, which have pkgconfig
filespkgconfig
files, but they are not accessible from clang64
environment (PKG_CONFIG_PATH
is set to /clang64/lib/pkgconfig:/clang64/share/pkgconfig$
, while ncurses-devel
package drops file into /usr/lib/pkgconfig
).
upd. clang64/mingw-w64-clang-x86_64-ncurses
have ncursesw.pc
, but no ncurses.pc
. I will try to use w
variant.
I tried to use ncursesw
, but looks like term.cc
compilation in Windows is broken anyway:
term.cc:194:20: error: expression is not assignable
194 | stdin = stdout = fdopen(scr_fd,"wr");
term.cc:195:5: error: use of undeclared identifier 'grantpt'
195 | grantpt(scr_fd);
| ^
term.cc:196:5: error: use of undeclared identifier 'unlockpt'
196 | unlockpt(scr_fd);
| ^
term.cc:197:60: error: use of undeclared identifier 'ptsname'
197 | fprintf(stderr, "\nBochs connected to screen \"%s\"\n",ptsname(scr_fd));
|
Looks like this is wrong path. My goal was to obtain Bochs binary with GUI debugger enabled without manual hacking. If console debugging will work, that's a bonus, but GUI mode on windows platform is more important I think.
This is what I see when I try to build Bochs with
--enable-debugger --enable-debugger-gui
with MSYS2 and clang:If I replace
-lreadline
with-lreadline -lncurses
, build finishes correctly.I did not figured out yet how to make correct change to build scripts.
Version: dbfb11f1ddd42f784af5089e24ec16cfaf683555