I occasionally encounter the error:
gcc -DPROGRAM='"bash"' -DCONF_HOSTTYPE='"x86_64"' -DCONF_OSTYPE='"linux-musl"'
-DCONF_MACHTYPE='"x86_64-pc-linux-musl"' -DCONF_VENDOR='"pc"'
-DLOCALEDIR='"/usr/local/share/locale"' -DPACKAGE='"bash"' -DSHELL
-DHAVE_CONFIG_H -I. -I. -I./include -I./lib
On 12/7/20 7:31 AM, Fazal Majid wrote:
I occasionally encounter the error:
gcc -DPROGRAM='"bash"' -DCONF_HOSTTYPE='"x86_64"' -DCONF_OSTYPE='"linux-musl"'
-DCONF_MACHTYPE='"x86_64-pc-linux-musl"' -DCONF_VENDOR='"pc"' -DLOCALEDIR='"/usr/local/share/locale"'
-DPACKAGE='"bash"' -DSHELL -DHAVE_CON
Introduction
The first public release of bash-5.1 is now available with the URLs
ftp://ftp.cwru.edu/pub/bash/bash-5.1.tar.gz
ftp://ftp.gnu.org/pub/gnu/bash/bash-5.1.tar.gz
and from the master branch of the bash git repository
(http://git.savannah.gnu.org/cgit/bash.git/log/)
and the
The first public release of the GNU Readline library, version 8.1, is
now available for FTP with the URLs
ftp://ftp.cwru.edu/pub/bash/readline-8.1.tar.gz
ftp://ftp.gnu.org/pub/gnu/readline/readline-8.1.tar.gz
and from the master branch in the readline git repository
(http://git.savannah.gnu.org/c
> On Dec 7, 2020, at 15:37, Chet Ramey wrote:
>
> On 12/7/20 7:31 AM, Fazal Majid wrote:
>> I occasionally encounter the error:
>> gcc -DPROGRAM='"bash"' -DCONF_HOSTTYPE='"x86_64"'
>> -DCONF_OSTYPE='"linux-musl"' -DCONF_MACHTYPE='"x86_64-pc-linux-musl"'
>> -DCONF_VENDOR='"pc"' -DLOCALEDIR='"/u
On 12/7/20 1:44 PM, Fazal Majid wrote:
On Dec 7, 2020, at 15:37, Chet Ramey wrote:
Thanks for the report. I've never actually encountered this error. Just
lucky, I guess.
It’s a race condition. The machine I run it on has 6 cores and HT, so I run it
with a `make -j 12`, and even then, it’s
On 12/7/20 1:47 PM, Benno Schulenberg wrote:
Hello Chet,
The first public release of bash-5.1 is now available with the URLs
ftp://ftp.cwru.edu/pub/bash/bash-5.1.tar.gz
ftp://ftp.gnu.org/pub/gnu/bash/bash-5.1.tar.gz
It would be nice if the Translation Project would get a CC for
the rc1 or r
Hello Chet,
> The first public release of bash-5.1 is now available with the URLs
>
> ftp://ftp.cwru.edu/pub/bash/bash-5.1.tar.gz
> ftp://ftp.gnu.org/pub/gnu/bash/bash-5.1.tar.gz
It would be nice if the Translation Project would get a CC for
the rc1 or rc2 release of bash, not for the final re
If I type in ( + are keypresses)
if [[ '' == $'\t' ]]; then echo ok; else echo notok; fi
bash displays:
if [[ ' ' == $'\t' ]]; then echo ok; else echo notok; fi
ok
if I now copy the 'if' line and paste it
if [[ ' ' == $'\t' ]]; then echo ok; else echo notok; fi
notok
if I take the same li
Configuration Information [Automatically generated, do not change]:
Machine: aarch64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security
uname output: Linux raspberrypi 5.4.72-v8+ #1356 SMP PREEMPT Thu Oct 22
13:58:52 BST 2020 aarch64 G$
Machine Type: aarch6
On Tue, Dec 8, 2020 at 10:04 AM Testing Purposes <
raspberry.teststr...@gmail.com> wrote:
> --
> readline.h defines a C preprocessor variable that should be treated as an
> integer,
As it says it's an integer.
> RL_READLINE_VERSION, which may be used to conditionally compile
> applicat
On Mon, Dec 7, 2020 at 9:30 PM Eastern Time, Clark Wang wrote:
The integer 0x801 is the same as 0x0801.
>
> # echo $(( 0x801 ))
> 2049
> # echo $(( 0x0801 ))
> 2049
> # echo $(( 0x0801 ))
> 2049
> #
>
>From an integer standpoint, I know that 08 (with one leading zero) is the
same as 8.
But
On Tue, Dec 8, 2020 at 12:36 PM Testing Purposes <
raspberry.teststr...@gmail.com> wrote:
> But Readline's official documentation specifically chose an example with a
> leading zero — 0x0402. It says that Readline 4.2 should have a version
> value of 0x0402, not 0x402.
>
Could you point me to wh
2020年12月8日(火) 10:04 Testing Purposes :
> Description:
>
> I just built Bash 5.1 [...], I ran "gdb bash" and entered
> "print /x (int) rl_readline_version". I get "0x801" as the output.
> If I do the same thing with Bash 5.0, I get "0x800".
>
> However, readline's online documentation at
>
On Tue, Dec 8, 2020 at 1:35 AM Eastern Time, Koichi Murase wrote:
> Because the information on the literal format used in the source code
> is lost in the executable `bash', you need to explicitly specify the
> format `0xMMmm' (i.e. %04x) to gdb like this:
>
> (gdb) printf "%04x\n", (int) rl_read
15 matches
Mail list logo