By default, gcc/ld will produce binaries which set e_type to ET_EXEC, which get detected as application/x-executable. When the command-line option -pie is used, a position-independent executable is created, which may, like shared libraries, be loaded at different addresses and still work. Because this works so much like a shared library, to avoid too many changes to the loader, such binaries get marked as ET_DYN, even though they can be executed directly.
If it is ET_DYN, then mimetype will treat it as a shared library.
...while on my VirtualMachine on my Toshiba notebook I have many trouble to install QB64 on it also following all your good tips... it lasts me to get direct help online from experts like Fifi.
But for now it is a must!
All that I have reached is to get QB64 into Programming folder, but it doesn't run in any way I call it.
I installed Mint 19 (the Cinnamon version) to test this out. I had no problems installing or running QB64 or the programs it generates, with the exception that the file manager prompted me each time I ran the binaries. Selecting "Make executable and run" works fine. Using the command line to launch things (or F5 inside the IDE) was no trouble at all. I did not modify any of the compiler flags.
The only bug I'm seeing here is with the file manager not correctly recognising an executable binary.
You should be fine with the stable build depending on the distro you've chosen to install. All of the above refers to the beta development version on a virtual machine, so it doesn't apply in general.