On 8/26/24 16:29, Chet Ramey wrote:
On 8/24/24 11:53 PM, Dennis Clarke via Bug reports for the GNU Bourne
Again SHell wrote:
This seemed to happen over and over and only during "make install".
There are a number of loadable builtins that require arrays and don't build
with
On 8/26/24 16:29, Chet Ramey wrote:
On 8/24/24 11:53 PM, Dennis Clarke via Bug reports for the GNU Bourne
Again SHell wrote:
This seemed to happen over and over and only during "make install".
There are a number of loadable builtins that require arrays and don't build
with
'/opt/bw/build/bash-5.2.32_rhel9_amd64.001/examples/loadables'
make: [Makefile:846: install] Error 2 (ignored)
Not very helpful.
This is off the shelf bone stock RHEL9 with the default compiler and
linker and nothing remotely interesting.
--
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
was happening over and over with different builds. Only on
that oddball hardware of course.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
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
MAILPATH CDPATH
+ eval test '${CDPATH+y}'
++ test
+ :
+ :
+ :
+ exec
+ :
+ :
+ PATH_SEPARATOR=:
+ as_myself=
+ case $0 in
+ as_myself=./configure
+ test x./configure = x
+ test '!' -f ./configure
malloc: ../bash-5.2.21/dispose_cmd.c:249: assertion botched
free: called with alrea
On 1/4/21 7:40 PM, Chet Ramey wrote:
> On 1/4/21 12:07 PM, Vladimir Marek wrote:
>> Hi,
>>
>> As a Solaris bash maintainer this interests me very much. I haven't yet
>> tried to upgrade bash to 5.1.x as there is no immediate need, sorry :)
>
> You might take a look at the changelog.
>
>> I'll try
On 12/31/20 12:31 AM, Chet Ramey wrote:
> On 12/29/20 7:28 PM, Dennis Clarke wrote:
>>
>> Firstly as a minor nit that seems to re-appear yearly there are still
>> source files in the release tarballs that are not readable to a normal
>> user :
>>
>> #
>
= (char *)NULL;
_rl_term_kh = _rl_term_kH = _rl_term_at7 = _rl_term_kI = (char *)NULL;
_rl_term_so = _rl_term_se = (char *)NULL;
#if defined(HACK_TERMCAP_MOTION)
_rl_term_forward_char = (char *)NULL;
#endif
For reasons that I can not yet figure out sh_get_env_value ("TER
name on it there Chet.
Anyways ... just wanted to utter a reminder that the tarball has some
restricted ./lib/glob/smatch.c in there as well as other ... stuff.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
Forwarded Message --
On 8/29/19 2:22 PM, Chet Ramey wrote:
BASH PATCH REPORT
=
Small problem when building bash-5.0-011 out of tree is that the
file lib/glob/smatch.c is set chmod 600 and thus not readable by
the build user.
--
Dennis
On 9/1/19 11:10 AM, 積丹尼 Dan Jacobson wrote:
$ ls *.pdf
a.pdf b.pdf
$ diff *.p
At this point should complete "*.pdf".
Or maybe as a bonus it could complete "a.pdf b.pdf" via a different key.
So long as all these extensions and ideas get turned off by the env var
POSIXLY_CORRECT then the sh
On 7/12/19 4:45 PM, Chet Ramey wrote:
On 7/12/19 4:26 PM, Martijn Dekker wrote:
Op 12-07-19 om 21:46 schreef Dennis Clarke:
Well the man page for XPG6 bc in Solaris 10 claims :
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment
variables that
On 7/12/19 4:45 PM, Chet Ramey wrote:
On 7/12/19 4:26 PM, Martijn Dekker wrote:
Op 12-07-19 om 21:46 schreef Dennis Clarke:
Well the man page for XPG6 bc in Solaris 10 claims :
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment
variables that
On 7/12/19 4:26 PM, Martijn Dekker wrote:
Op 12-07-19 om 21:46 schreef Dennis Clarke:
Well the man page for XPG6 bc in Solaris 10 claims :
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment
variables that affect the execution of bc: LANG, LC_ALL
On 7/12/19 3:50 PM, Chet Ramey wrote:
On 7/12/19 3:46 PM, Dennis Clarke wrote:
uh huh ...
LC_NUMERIC
This category specifies the decimal and thousands
delimiters. The information corresponding to this
category is stored in a database
RIC=fr_FR.UTF-8 /usr/xpg6/bin/bc -l
a = 0,1
syntax error on line 1, teletype
a = 0.1
b = 0.11
c = a + b
c
.21
c(c)
.97803091472414824491
corv $
baloney. :-)
I am going to look at the sources for bc just for the fun of it.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
n/bc -l
a = 0,1
syntax error on line 1, teletype
a = 0.1
b = 0.01
c = a + b
c
.11
c(c)
.99395609795669685035
corv $
Well now. That is XPG6 compliant bc on Solaris 10 sparc.
It could care less about locale it seems. Nifty.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
On 5/25/19 5:55 PM, Chet Ramey wrote:
On 5/25/19 2:06 PM, Dennis Clarke wrote:
On any Solaris boxen there really isn't O_CLOEXEC so even after a neat
compile and test the install will blow up.
http://lists.gnu.org/archive/html/bug-bash/2019-02/msg00167.html
You can use the patch there
0-007_SunOS5.10_sparc64vii+.002/examples/loadables'
gmake: [Makefile:824: install] Error 2 (ignored)
beta #
Yeah well. Okay.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
has left the building and all the great Solaris guys were
taken to the chemical shed and shot. Oracle Solaris is a dead product.
Good luck getting the userbase back. Oracle did *everything* to kill it.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
On 4/22/19 1:26 PM, Greg Wooledge wrote:
On Mon, Apr 22, 2019 at 01:21:38PM -0400, Dennis Clarke wrote:
I don't think bash 5 has hit Debian sid yet.
It's not only in sid; it's also in buster.
Here's the relevant excerpt from the changelog:
bash (5.0-1) unstable; urgency=
On 4/22/19 1:01 PM, Greg Wooledge wrote:
On Mon, Apr 22, 2019 at 12:54:28PM -0400, Dennis Clarke wrote:
I see these are all published in the gnu ftp server :
https://ftp.gnu.org/pub/gnu/bash/bash-5.0-patches/
So I will try again from the sources but am curious if there is a definitive
On 4/22/19 9:53 AM, Chet Ramey wrote:
BASH PATCH REPORT
=
Bash-Release: 5.0
Patch-ID: bash50-007
I see these are all published in the gnu ftp server :
https://ftp.gnu.org/pub/gnu/bash/bash-5.0-patches/
So
etc
Most likely we need a check for the existence of O_CLOEXEC during the
configure stage and then adjust ./examples/loadables/Makefile.in to
remove or skip the example file.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
25 matches
Mail list logo
