Use no-shared to stop getting libcrypto and libssl linked dependencies

[ericbeland]

I set the compile options to no-shared. It looks like this removed the dependencies. The executable runs on my machine, but I need to do more testing.

Before

otool -L /Users/ebeland/apps/ruby-packer/rubyc
/Users/ebeland/apps/ruby-packer/rubyc:
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1858.112.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1311.100.3)
/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
/var/folders/s9/mtk8pgj529j4lq_b7bl2fkkc0000gn/T/rubyc/local/lib/libssl.1.1.dylib (compatibility version 1.1.0, current version 1.1.0)
/var/folders/s9/mtk8pgj529j4lq_b7bl2fkkc0000gn/T/rubyc/local/lib/libcrypto.1.1.dylib (compatibility version 1.1.0, current version 1.1.0)
/usr/lib/libutil.dylib (compatibility version 1.0.0, current version 1.0.0)

After

otool -L /Users/ebeland/apps/ruby-packer/rubyc
/Users/ebeland/apps/ruby-packer/rubyc:
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1858.112.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1311.100.3)
	/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
	/usr/lib/libutil.dylib (compatibility version 1.0.0, current version 1.0.0)

---

I also turned off some debug settings to see if we could get a little smaller executable. It works, but the difference isn't major.

[ericbeland]

@taraszka, it might be fixed here. Does this look off-base in any way to you? It seems to have removed the visible dependencies and works on my machine so far.