bug#22354: Test failure when running distcheck from out-of-tree build

2016-01-13 Thread Taylan Ulrich Bayırlı/Kammer
l...@gnu.org (Ludovic Courtès) writes: > taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis: > >> l...@gnu.org (Ludovic Courtès) writes: >> >>> taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis: >>> If one runs distcheck from within the build directory of an out-o

bug#22354: Test failure when running distcheck from out-of-tree build

2016-01-13 Thread Ludovic Courtès
taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis: > ./configure: ./config.status: > /home/taylan/src/guix/build/guix-0.9.1/_build/sub/test-tmp/store/d41iyl2gyk0

bug#22354: Hash-bang line length

2016-01-13 Thread Ludovic Courtès
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?

bug#22354: Test failure when running distcheck from out-of-tree build

2016-01-13 Thread Taylan Ulrich Bayırlı/Kammer
l...@gnu.org (Ludovic Courtès) writes: > taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis: > >> Yes, it still goes through the tests and fails at guix-environment.sh >> with the same error. I repeated all steps from a new clone of master. >> >> taylan@T420:~/src/guix/build$ grep l

bug#20433: Keyboard not working on laptop with guixSD

2016-01-13 Thread Jessica Tallon
Ludovic Courtès writes: > Hi! > > Jessica Tallon skribis: > >> I just checked in Trisquel as I was curious what driver was being used >> there and `lsusb -t` shows the driver to be usbhid module. I confirmed >> this by unloading the module and verifying the keyboard stopped >> working. >> >> I di

bug#22354: Hash-bang line length

2016-01-13 Thread Ludovic Courtès
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 >> in the Linux kernel¹ and can quite

bug#22354: Hash-bang line length

2016-01-13 Thread Greg Wooledge
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 > in the Linux kernel¹ and can quite easily be hit². That's actually

bug#22354: Hash-bang line length

2016-01-13 Thread Greg Wooledge
On Wed, Jan 13, 2016 at 02:52:08PM +0100, Ludovic Courtès wrote: > Sure, but the fact that it???s smaller than that of the kernel Linux is > problematic: when a hash-bang line > 127 chars is encountered, ???execve??? > fails with ENOENT, so Bash???s fallback code is executed, fails as well, > but i

bug#20433: Keyboard not working on laptop with guixSD

2016-01-13 Thread Ludovic Courtès
Jessica Tallon skribis: > Sure, I have attached both the lsmod on trisquel where it does work and > the lsmod in the guix 0.9 image where it doesn't. I did try and look > what additional modules trisquel have to see if any stood out but none > of them did. The list of modules present and Trisque

bug#22354: Hash-bang line length

2016-01-13 Thread Greg Wooledge
On Wed, Jan 13, 2016 at 11:23:34AM -0500, Chet Ramey wrote: > On 1/13/16 9:04 AM, Greg Wooledge wrote: > > On Wed, Jan 13, 2016 at 02:52:08PM +0100, Ludovic Courtès wrote: > >> Sure, but the fact that it???s smaller than that of the kernel Linux is > >> problematic: when a hash-bang line > 127 char

bug#22354: Hash-bang line length

2016-01-13 Thread Ludovic Courtès
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.c reads at most 80 bytes from the hash-bang line. T

bug#22354: Hash-bang line length

2016-01-13 Thread Chet Ramey
On 1/13/16 9:04 AM, Greg Wooledge wrote: > On Wed, Jan 13, 2016 at 02:52:08PM +0100, Ludovic Courtès wrote: >> Sure, but the fact that it???s smaller than that of the kernel Linux is >> problematic: when a hash-bang line > 127 chars is encountered, ???execve??? >> fails with ENOENT, so Bash???s fal

bug#22354: Hash-bang line length

2016-01-13 Thread Chet Ramey
On 1/13/16 5:25 AM, 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 > in the Linux kernel¹ and can quite easily be hit². That limit is huge compared to other Unix

bug#22354: Hash-bang line length

2016-01-13 Thread Chet Ramey
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.c reads at most 80 bytes from >>> the hash-bang line. This is less than the already-small 12

bug#22366: Chicken Scheme release tarballs ship non-source C code

2016-01-13 Thread Thompson, David
Because Chicken Scheme's compiler is self-hosting, and because it compiles to C as an intermediate form, the maintainers circumvented the bootstrapping problem by shipping generated C code for the compiler. Many *.c files feature a comment that starts like this: Generated from optimizer.scm b

bug#22354: Hash-bang line length

2016-01-13 Thread Chet Ramey
On 1/13/16 12:41 PM, Ludovic Courtès wrote: >>> but it prints a misleading error message with an even more truncated >>> hash-bang line. >> >> Again, it's only a cosmetic issue. I don't have a problem with increasing >> the buffer size, but let's not pretend it's anything but that. > > Exactly.