You are not logged in.
building linux 4.14.10 fails with
make[2]: execvp: ./sync-check.sh: Permission denied
because the script is not executable, this is the change https://git.kernel.org/pub/scm/linux/ke … 3f361c102b
$ stat src/linux-4.14/tools/objtool/sync-check.sh
File: src/linux-4.14/tools/objtool/sync-check.sh
Size: 584 Blocks: 8 IO Block: 4096 regular file
Device: fe01h/65025d Inode: 70535113 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1001/ testuser) Gid: ( 1001/ testuser)
Access: 2017-12-29 19:08:37.543226697 +0000
Modify: 2017-12-29 19:08:37.543226697 +0000
Change: 2017-12-29 19:08:37.543226697 +0000
Birth: -but checking patch adding --verbose
Hmm... The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/tools/objtool/sync-check.sh b/tools/objtool/sync-check.sh
|new file mode 100755
|index 000000000000..1470e74e9d66
|--- /dev/null
|+++ b/tools/objtool/sync-check.sh
--------------------------
patching file tools/objtool/sync-check.sh
Using Plan A...
Hunk #1 succeeded at 1.I can change the PKGBUILD to fixup the permissions but I would like to understand why they are not correct after patch creates the file.
Edit:
switching patch to
git apply "${srcdir}/patch-${pkgver}"creates the file 755.
Last edited by loqs (2017-12-29 20:36:19)
Offline
Might the filesystem where you are trying to build be mounted with noexec?
Edit:
Nope, that's not the problem, fails here and I'm sure the filesystem is not mounted with noexec.
Last edited by R00KIE (2017-12-29 20:17:05)
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Rookie no there is no filesystem limitation as proven by git apply creating the file correctly. It seems patch is creating the file with default permissions looking through the patch man page I can not find anything covering permissions.
Offline
Yep, apparently GNU patch doesn't support file permissions. Arch kernel maintainers are aware of it.
Last edited by Scimmia (2017-12-29 20:56:48)
Offline
Scimmia thank you for the confirmation / explanation.
Offline
There's some researching going on in #archlinux, apparently GNU patch supports changing the file mode of an existing file, but not applying it when creating a new file. They're not sure yet if it's a bug or an unimplemented feature.
Offline