On 7/24/25 9:07 AM, Joshua Newton wrote:
Just to verify I'm understanding correctly, the recommendation is that both bash and readline should be updated in lockstep, and so by attempting to hold back readline but not bash, I'm just exacerbating the problem? (i.e. bash 5.3 + readline 8.2 == X)
Yes. If you get an error like this, a program (sh) is trying to satisfy an unresolved symbol (rl_print_keybinding), but it's not present in any of the libraries it has linked. Since this symbol was introduced in readline-8.3, it's logical to conclude that bash-5.3 is trying to use readline-8.2.
What is strange to me is that, in my initial comparison between passing and failing runs, I noticed that both bash and readline were getting updated to 5.3 and 8.3 in lockstep, and yet the error stilloccurred: https://www.diffchecker.com/cn6N5NUb/.
I'd run `ldd' or equivalent to check which shared libraries that instance
of bash has linked.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
OpenPGP_signature.asc
Description: OpenPGP digital signature
