Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Baldwin <jhb@freebsd.org>
To: Pedro Alves <palves@redhat.com>
Cc: Matthias Klose <doko@ubuntu.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Allow to link with ncursesw
Date: Wed, 20 Sep 2017 23:58:00 -0000	[thread overview]
Message-ID: <3057121.ifSOzBUOOt@ralph.baldwin.cx> (raw)
In-Reply-To: <e8d80005-3c3a-cff7-0164-858280117d89@redhat.com>

On Wednesday, September 20, 2017 10:22:29 PM Pedro Alves wrote:
> On 09/20/2017 08:51 PM, Matthias Klose wrote:
> > On 20.09.2017 20:39, Pedro Alves wrote:
> 
> >> Did you reach out to readline/bash, see if they're willing
> >> to try ncursesw before ncurses too?  Don't we need at least
> >> a local patch to our local readline copy, to avoid breaking
> >> those that use it and have it link with ncurses?
> > 
> > afaik, this is only the case if readline is linked with one of the curses
> > libraries.  However these days everybody seems to have readline linked to just
> > tinfo, so this shouldn't be an issue?
> 
> Everybody on GNU/Linux, it seems.  However, the Python bug
> report talked about FreeBSD's readline linked with ncurses
> Do you know whether they've switched to tinfo as well
> meanwhile?  [Adding John as FreeBSD maintainer.]

FreeBSD still links libreadline against curses:

% ldd /usr/local/lib/libreadline.so.7
/usr/local/lib/libreadline.so.7:
        libncursesw.so.8 => /lib/libncursesw.so.8 (0x801251000)
        libc.so.7 => /lib/libc.so.7 (0x800825000)

However, it seems to be linked against libncursesw.  gdb on this same
system (11.1) is linked against both ncurses libraries:

% ldd /usr/local/bin/gdb80 
/usr/local/bin/gdb80:
        libreadline.so.7 => /usr/local/lib/libreadline.so.7 (0x801dda000)
        libncurses.so.8 => /lib/libncurses.so.8 (0x80202b000)
        libkvm.so.7 => /lib/libkvm.so.7 (0x802281000)
        libutil.so.9 => /lib/libutil.so.9 (0x80248f000)
        libm.so.5 => /lib/libm.so.5 (0x8026a3000)
        libthr.so.3 => /lib/libthr.so.3 (0x8028cd000)
        libintl.so.8 => /usr/local/lib/libintl.so.8 (0x802af5000)
        libpython2.7.so.1 => /usr/local/lib/libpython2.7.so.1 (0x802d00000)
        libexpat.so.1 => /usr/local/lib/libexpat.so.1 (0x8030e3000)
        liblzma.so.5 => /usr/lib/liblzma.so.5 (0x80330e000)
        libc++.so.1 => /usr/lib/libc++.so.1 (0x803537000)
        libcxxrt.so.1 => /lib/libcxxrt.so.1 (0x803801000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x803a20000)
        libc.so.7 => /lib/libc.so.7 (0x803c2f000)
        libncursesw.so.8 => /lib/libncursesw.so.8 (0x803fec000)
        libelf.so.2 => /lib/libelf.so.2 (0x80424b000)

Given that readline on FreeBSD now uses ncursesw and that the original
python report was from several years ago when that probably wasn't true,
I'm inclined to think that using ncursesw might be fine.  I'll try a test
build of this patch tomorrow.

-- 
John Baldwin


  parent reply	other threads:[~2017-09-20 23:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 10:29 Matthias Klose
2017-09-20 18:39 ` Pedro Alves
2017-09-20 19:52   ` Matthias Klose
2017-09-20 21:22     ` Pedro Alves
2017-09-20 21:25       ` Pedro Alves
2017-09-20 23:58       ` John Baldwin [this message]
2017-09-22 10:22         ` Pedro Alves
2017-09-25 18:34           ` John Baldwin
2017-09-26 15:27             ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3057121.ifSOzBUOOt@ralph.baldwin.cx \
    --to=jhb@freebsd.org \
    --cc=doko@ubuntu.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox