[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bash-5.2.9 lib/readline/input.c fix for Tru64

From: Koichi Murase
Subject: Re: bash-5.2.9 lib/readline/input.c fix for Tru64
Date: Tue, 15 Nov 2022 12:01:02 +0900

2022年11月15日(火) 9:04 Henry Bent <henry.r.bent@gmail.com>:
> In bash-5.2.9 if HAVE_SELECT is set but HAVE_PSELECT is not, we still need
> the "fd_set readfds;" at line 808 in lib/readline/input.c.  Found on Tru64
> 5.1.

This seems to be reported repeatedly for different lines in the source code.


I think someone needs to finally check the fixed version actually
compiles in a real Tru64 machine. I attach a possible patch
[202211-0044.HAVE_PSELECT-in-True64.patch] but haven't tested it in
Tru64, so I'm not sure if this is all.

> This
> is because the Tru64 linker will still produce an executable and return
> true even if the executable contains unresolved symbols.  I'm not
> immediately sure of a fix for that one.

I guess that should be fixed at the side of autoconf. I thought the
configure script in the distributed version of Bash might be old so
checked it, but it is actually generated by the latest version of
autoconf-2.71 (2021-01). This can be a regression of autoconf because
these STRTO* tests seem to have existed for at least twenty years
(according to git blame config.h.in) and bash seems to have worked in
Tru64 for this period. Maybe you could try an older version of
autoconf (e.g. 2.69) to regenerate the configure script.


Attachment: 202211-0044.HAVE_PSELECT-in-True64.patch.txt
Description: Text document

reply via email to

[Prev in Thread] Current Thread [Next in Thread]