On 2/29/24 12:11 PM, Dennis Clarke via Bug reports for the GNU Bourne Again
SHell wrote:
Well this has me a bit baffled.
I downloaded the bash source tarball for 5.2.21 and then applied the few
patches to get me to :
io$
io$ which bash
/opt/bw/bin/bash
io$ bash --version
GNU bash, version 5.
On 3/4/24 12:05 PM, Chet Ramey wrote:
It might be something as simple as using an old version of bison, for
example.
Or does your config happen to be using LD_PRELOAD?
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet
On 3/4/24 12:05, Chet Ramey wrote:
On 2/29/24 12:11 PM, Dennis Clarke via Bug reports for the GNU Bourne
Again SHell wrote:
Well this has me a bit baffled.
I downloaded the bash source tarball for 5.2.21 and then applied the
few patches to get me to :
io$
io$ which bash
/opt/bw/bin/bash
io$
On 3/4/24 12:56, Chet Ramey wrote:
On 3/4/24 12:05 PM, Chet Ramey wrote:
It might be something as simple as using an old version of bison, for
example.
Or does your config happen to be using LD_PRELOAD?
No no ... nothing bonkers like that. In fact the whole env is very very
basic as this
On 3/4/24 1:06 PM, Dennis Clarke wrote:
What I shall do is look at the dependency tree for bison 3.8.2 and build
everything from bottom to top. Then get into a valgrind build and see
what happens. Good advice. Thank you. Half of the problem is that the
hardware is weird! Not sure who else bother
On Mon, Mar 4, 2024, 19:07 Dennis Clarke via Bug reports for the GNU Bourne
Again SHell wrote:
> On 3/4/24 12:05, Chet Ramey wrote:
> > On 2/29/24 12:11 PM, Dennis Clarke via Bug reports for the GNU Bourne
> > Again SHell wrote:
> >>
> >> Well this has me a bit baffled.
> >>
> >> I downloaded the
