Jeffrey, > Le 14 janv. 2021 à 02:21, Jeffrey Walton <noloa...@gmail.com> a écrit : > > Hi Everyone/Akim, > > I was looking at Bison 3.7.4 autoconf options versus link libraries. > > $ ldd /usr/local/bin/bison > linux-vdso.so.1 > libiconv.so.2 => /usr/local/bin/../lib/libiconv.so.2 > libtextstyle.so.0 => /usr/local/bin/../lib/libtextstyle.so.0 > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 > libtinfow.so.6 => /usr/local/bin/../lib/libtinfow.so.6 > /lib64/ld-linux-x86-64.so.2 > > The libtinfow is from Ncurses, but adding --with-libncurses-prefix=DIR > to configure results in: > > WARNING: unrecognized options: --with-libncurses-prefix
Well, we really don't use libncurses here. libtinfow might indeed come from there, but it is not it, so I personally don't think there is a problem. That being said, bison was probably not linked against it directly. Grep did not find occurrences of tinfow in Bison's tarball. It was most probably inherited from libtextstyle.so.0, so that's where you should look for such a feature.
