Binaries output by deno compile don't pass strict MachO validation on macOS

[jhheider]

Apple even warns in the manpage that --strict is a moving target; however, other major language binaries don't exhibit this issue:

$ echo 'console.log("hello")' >foo.js
$ deno compile -o foo foo.js
Compile file:///Users/jacob/foo/foo.js
Emit foo
$ ./foo
hello
$ codesign -fv -s - foo
foo: replacing existing signature
foo: main executable failed strict validation

Google searching, but no actual exploration of the header, suggests that having the wrong segment last is one of the common issues. I'm not sure I have the deep knowledge to dig further into this, but I'll look into as my time permits.

[aapoalas]

This may be related to #575

[mxcl]

From Apple docs:

codesign says my main executable failed strict validation.

• Your Mach-O executable does not conform to modern Mach-O layout rules.
• You may be using a third party development product that hasn't been brought up to date, or post-processed your file in unsupported ways.

[mxcl]

Confirmed this is fixed with deno^2