[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #57022] Error 127 executing a script with no #!
From: |
Martin Dorey |
Subject: |
[bug #57022] Error 127 executing a script with no #! |
Date: |
Fri, 11 Oct 2019 14:09:39 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36 |
Follow-up Comment #5, bug #57022 (project make):
Argh, all those hours fighting autoconf to now see Dmitry had already sent a
similar patch. I see Paul didn't like the cross-compilation issue. That was
when it just looked like an ENOENT problem, which he could sensibly solve at
runtime, before the ENOEXEC aspect came up. I intended my patch to leave
posix_spawn enabled in the cross-compilation case, which is perhaps more in
line with Paul's forward-looking preference. I leaked a copy of the filename
because I'm really a C++ programmer, whose string literals are const.
Dmitry's use of '\0' for a char* seemed a bit odd to me. His patch generated
the right value for USE_POSIX_SPAWN in src/config.h for me on both my test
systems.
(file #47652)
_______________________________________________________
Additional Item Attachment:
File name: dmitry.patch Size:1 KB
<https://savannah.gnu.org/file/dmitry.patch?file_id=47652>
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57022>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/