If you run a 64-bit executable on a 32-bit system via bash (which
can happen by accident), it gives an "bash: ./fwupd: cannot execute
binary file" error message. What seems to happen is that the execve()
function in execute_cmd.c returns 8, and in this case bash only tests if
the file is a script or binary. An ENOEXEC-like message of "An
executable is not in a recognized format, or is for the wrong
architecture" or at least the ENOEXEC string would be more helpful in
determining the cause of the problem.