nable-history --enable-strict-posix-default \
> >> > --enable-threads=posix --with-curses --with-gnu-ld
> >>
> >> This is a pretty darn minimal config there.
> >>
> >> When I try to use that shell ( for just about anything ) I get 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 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
nimal config there.
When I try to use that shell ( for just about anything ) I get this
message very often :
malloc: ../bash-5.2.21/dispose_cmd.c:249: assertion botched
free: called with already freed block argument
I can't reproduce this on a generic RHEL system using this configuration,
bu
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
e that shell ( for just about anything ) I get this
message very often :
malloc: ../bash-5.2.21/dispose_cmd.c:249: assertion botched
free: called with already freed block argument
I can't reproduce this on a generic RHEL system using this configuration,
but that's probably not close enoug
:
+ for as_var in BASH_ENV ENV MAIL MAILPATH CDPATH
+ eval test '${MAIL+y}'
./configure: line 68: bad substitution: no closing `}' in ��
+ :
+ for as_var in BASH_ENV ENV MAIL MAILPATH CDPATH
+ eval test '${MAILPATH+y}'
++ test
+ :
+ for as_var in BASH_ENV ENV MAIL
