Re: Hash-bang line length

Chet Ramey skribis: > On 1/13/16 8:52 AM, Ludovic Courtès wrote: >> Greg Wooledge skribis: >> >>> On Wed, Jan 13, 2016 at 11:25:03AM +0100, Ludovic Courtès wrote: >>>> Hello, >>>> >>>> The ???READ_SAMPLE_BUF??? macro in execute_cmd

Re: Hash-bang line length

Greg Wooledge skribis: > On Wed, Jan 13, 2016 at 11:25:03AM +0100, Ludovic Courtès wrote: >> Hello, >> >> The ???READ_SAMPLE_BUF??? macro in execute_cmd.c reads at most 80 bytes from >> the hash-bang line. This is less than the already-small 128-byte limit >> i

Hash-bang line length

Hello, The ‘READ_SAMPLE_BUF’ macro in execute_cmd.c reads at most 80 bytes from the hash-bang line. This is less than the already-small 128-byte limit in the Linux kernel¹ and can quite easily be hit². What about changing it to 128 bytes (as well as the ‘sample’ array) to at least match Linux?

Re: Installation of PDF/PS/DVI and HTML files

Chet Ramey skribis: > On 12/3/15 6:05 AM, Ludovic Courtès wrote: [...] >> In addition, the ‘install’ rule in doc/Makefile.in would need to be >> split in ‘install-info’, ‘install-pdf’, etc. (as explained in the GCS), >> with ‘install’ depending only on ‘install-info’.

Re: Installation of PDF/PS/DVI and HTML files

Chet Ramey skribis: > On 12/4/15 4:24 AM, Ludovic Courtès wrote: >> Greg Wooledge skribis: >> >>> On Thu, Dec 03, 2015 at 01:08:13PM +0200, Ludovic Courtès wrote: >>>> Given that the GCS suggests installing only the Info version of the >>>> manua

Re: Installation of PDF/PS/DVI and HTML files

Greg Wooledge skribis: > On Thu, Dec 03, 2015 at 01:08:13PM +0200, Ludovic Courtès wrote: >> Given that the GCS suggests installing only the Info version of the >> manual by default (info "(standards) Standard Targets") > >> What do you think? > > I t

Installation of PDF/PS/DVI and HTML files

Hello, Akira of Debian noticed that ‘make all’ rebuilds and install PDF/PS/DVI/HTML documentation by default, which prevents default Bash builds from being bit-reproducible¹. Given that the GCS suggests installing only the Info version of the manual by default (info "(standards) Standard Targets"

Installation of PDF/PS/DVI and HTML files

Hello, Akira of Debian noticed that ‘make all’ rebuilds and install PDF/PS/DVI/HTML documentation by default, which prevents default Bash builds from being bit-reproducible¹. Given that the GCS suggests installing only the Info version of the manual by default (info "(standards) Standard Targets"

Installing Bash headers for loadable builtins

Hi, What’s the right way to install Bash headers so that third-party builtins can be built (as loadable shared objects)? I didn’t see any mention of it in INSTALL nor in the manual, and there doesn’t seem to be a makefile rule to install them. Thanks, Ludo’.

Re: Source code repository

Hello, Eric Blake writes: > On 03/13/2010 11:48 AM, Ludovic Courtès wrote: [...] >> Do you mean there exists a private repository with more detailed >> history? > > Does it matter, if it isn't made public? It would matter if we could find an arrangement to publish

Re: Source code repository

Hi Eric, Eric Blake writes: > On 03/12/2010 08:59 AM, Ludovic Courtès wrote: [...] >> I’m building from git://git.sv.gnu.org/bash.git but I’m wondering >> whether this is the repository that you actually use, given that it >> hasn’t been touched in 6 months and the log

Source code repository

Hello, I’m in the process of setting up continuous builds of Bash on Hydra [0], which can be seen at . I’m building from git://git.sv.gnu.org/bash.git but I’m wondering whether this is the repository that you actually use, given that it hasn’t been t