The usage of `cd builtins && $(MAKE) ...`

Hi, I see things like `cd builtins && $(MAKE) ...` in the Makefiles in bash source code. GNU Make has the option of -C for entering a directory and make. Is the reason to cd then make for compatibility with other make's that don't support -C? Thanks. -- Regards, Peng

Re: The usage of `cd builtins && $(MAKE) ...`

Hi, > I see things like `cd builtins && $(MAKE) ...` in the Makefiles in > bash source code. GNU Make has the option of -C for entering a > directory and make. Is the reason to cd then make for compatibility > with other make's that don't support -C? Thanks. I'm afraid that you are in wrong maili

"COMMAND 2>&1 > PATH" doesn't work

Hello. If I try in bash this command ex. "rmdir somethingA > somethingA.out 2>&1" work right. But, if I try "rmdir somethingB 2>&1 > somethingB.out" that work wrong. That work's wrong in Bash version 4.4.23(1) and too in 5.0.0(1)-rc1: # v. 4.4.23(1) # $ mkdir /dev/shm/test $ cd

Re: "COMMAND 2>&1 > PATH" doesn't work

On Sun, Dec 30, 2018 at 10:10:42PM +0100, Dušan Kreheľ wrote: > Hello. > > If I try in bash this command ex. "rmdir somethingA > somethingA.out > 2>&1" work right. But, if I try "rmdir somethingB 2>&1 > > somethingB.out" that work wrong. > > That work's wrong in Bash version 4.4.23(1) and too in

Re: bug in dirname loadable?

On Wed, Dec 26, 2018 at 11:35 AM Chet Ramey wrote: > > On 12/24/18 10:35 PM, Peng Yu wrote: > > dirname loadable gives the following error. I think the coreutils' > > direname's convention is better. Should it be considered as a bug to > > fix? > > > > $ dirname -- -a > > dirname: usage: dirname s

Reading from a file by using its FD returns its contents only once

Configuration Information: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I