[bug #53201] Target runs incorrect command when shebang line exceeds kernel limit

2018-08-04 Thread Paul D. Smith
Update of bug #53201 (project make): Status:None => Works for me Open/Closed:Open => Closed ___ Follow-up Comment #5: I re-examined the

[bug #53201] Target runs incorrect command when shebang line exceeds kernel limit

2018-04-08 Thread Paul D. Smith
Follow-up Comment #4, bug #53201 (project make): I don't understand the issue being reported. It would be greatly illuminating if you could provide an example of the extra-long shebang line for me to examine. I've tried for a bit to reproduce the problem and cannot. It's not clear from your

Re: [bug #53201] Target runs incorrect command when shebang line exceeds kernel limit

2018-03-17 Thread Casey McGinty
Interesting observation but I don’t follow how that is related to this issue. The interpreter is not yet running in this case. On March 17, 2018 at 10:12:54 AM, Brian Vandenberg ( phantall+gnum...@gmail.com) wrote: I cannot remark on pip specifically, but some script interpreters seem to

Re: [bug #53201] Target runs incorrect command when shebang line exceeds kernel limit

2018-03-17 Thread Brian Vandenberg
I cannot remark on pip specifically, but some script interpreters seem to ignore the shebang line if the script is passed as an argument: $ cat /tmp/blah.sh #!/bin/bash printf( "%s:%d\n", __FILE__, __LINE__ ); $ /tmp/blah.sh /tmp/blah.sh: line 2: syntax error near unexpected token `"%s:%d\n",'

[bug #53201] Target runs incorrect command when shebang line exceeds kernel limit

2018-02-22 Thread David Boyce
Follow-up Comment #3, bug #53201 (project make): Sorry, I was thinking of a different kernel limit but my second observation, that the difference observed has to do with fast path optimization, remains. Working around it by setting SHELL=//bin/sh in the makefile is probably safer than .ONESHELL.

[bug #53201] Target runs incorrect command when shebang line exceeds kernel limit

2018-02-22 Thread thutt
Casey McGinty writes: > Follow-up Comment #2, bug #53201 (project make): > > See http://man7.org/linux/man-pages/man2/execve.2.html > > *A maximum line length of 127 characters is allowed for the first line in an > interpreter script.* I think this is referring to the '#!' line of a

[bug #53201] Target runs incorrect command when shebang line exceeds kernel limit

2018-02-21 Thread Casey McGinty
Follow-up Comment #2, bug #53201 (project make): See http://man7.org/linux/man-pages/man2/execve.2.html *A maximum line length of 127 characters is allowed for the first line in an interpreter script.* My kernel is Linux 3.10.0-693.2.2.el7.x86_64 #1 SMP Tue Sep 12 22:26:13 UTC 2017 x86_64

[bug #53201] Target runs incorrect command when shebang line exceeds kernel limit

2018-02-21 Thread David Boyce
Follow-up Comment #1, bug #53201 (project make): I think a couple of facts here may need correcting though the issue is quite real. I suspect you are not running into a kernel limit since modern Linux kernels have no such limit (at one time the limit was 131K, then doubled to 262K, then removed

[bug #53201] Target runs incorrect command when shebang line exceeds kernel limit

2018-02-20 Thread Casey McGinty
URL: Summary: Target runs incorrect command when shebang line exceeds kernel limit Project: make Submitted by: cmcginty Submitted on: Wed 21 Feb 2018 07:35:13 AM UTC Severity: 3 -