This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Linking gdb with -ltinfow, if libtinfo is not available
Hello,
you should be able to test this by having libtinfo.so in a directory,
that is not introduced to the linker by -L and is not default for the
compiller or linker and have libtinfow.so in а path passed by -L;
possibly moving libtinfo.so to a location that is still considered by
ldconfig.
Regards
Дилян
On Wed, 2018-12-05 at 09:49 -0500, Simon Marchi wrote:
> On 2018-12-05 02:22, Дилян Палаузов wrote:
> > See https://sourceware.org/bugzilla/show_bug.cgi?id=23950 for details.
> >
> > diff --git a/gdb/configure.ac b/gdb/configure.ac
> > --- a/gdb/configure.ac
> > +++ b/gdb/configure.ac
> > @@ -592,7 +592,7 @@ case $host_os in
> > esac
> >
> > # These are the libraries checked by Readline.
> > -AC_SEARCH_LIBS(tgetent, [termcap tinfo curses ncursesw ncurses])
> > +AC_SEARCH_LIBS(tgetent, [termcap tinfo tinfow curses ncursesw
> > ncurses])
> >
> > if test "$ac_cv_search_tgetent" = no; then
> > CONFIG_OBS="$CONFIG_OBS stub-termcap.o"
>
> I am not able to test this (since all my systems have a libtinfo.so,
> which gets picked up), but I think it makes sense. If you have a system
> where the only ncurses available is configured with:
>
> --with-termlib --with-shared --enable-widec
>
> you end up with libtinfow.so and no libtinfo.so. Any objections? I can
> take care of ChangeLog and commit message since it is a very small
> change, but next time please make sure to follow the checklist [1].
>
> Thanks,
>
> Simon
>
> [1] https://sourceware.org/gdb/wiki/ContributionChecklist