On Sat, Aug 20, 2016 at 03:25:25PM +0200, Jeremie Courreges-Anglas wrote:
> Pretty much any time you see this, you can assume that the kernel
> returned ENOEXEC.  This can happen with an invalid executable,
> a partition mounted "noexec", or... a program annotated with wxneeded
> but placed on a partition that isn't mounted with "wxallowed".  Check
> the partition that holds WRKOBJDIR (probably /home here).

Great tip, thank you very much. The diff is now just a USE_WXNEEDED
addition :-)

Frank

Reply via email to