Reported in the OTN forum:
=======
The packaging step on Debian Linux system succeeds for me, and it installs, but when I run the resulting program (which the installer puts in /opt/myprog/myprog), I get
jvm.dll is not found [/opt/myprog/runtime/jre/lib/amd64/client/libjvm.so]
Failed to launch JVM which is a pretty weird error, given that .dll is a Windows notion.
I get the same error if I try to just run the "standalone" image that the packager leaves in deploy/bundles/myprog.
=======

There are 2 issues here:
   a) minor - error message should report on .so and not .dll
   b) big - we never lookup for jvm.so in the server folder! Lookup in the same "client" folder twice
       This will not work if JRE does not have client JVM as 64 bit JRE does
       (i think it is only applicable to linux launcher but i might be wrong)

Possible workaround (not tested):
   Provide custom "post install script" and create symlink [/opt/myprog/runtime/jre/lib/amd64/client/ pointing to [/opt/myprog/runtime/jre/lib/amd64/server).

Another workaround - use 32 bit JRE for bundle (unless you have 64-bit native libs)