Return to Answer

> ./m./minecraft-pi 
./minecraft-pi: error while loading shared libraries: libGLESv2.so: cannot open shared object file: No such file or directory

That list is abbreviated but you van see there are a few things not found; libSDL is closely related to openGL(ES) and libpng is for .png images.

To check for which packag libGLESv2.so is in:

• Try and install a 32-bit userland ("userland" = software besides the kernel, which a 64-bit kernel can run 32-bit executables if all the dependencies are me): https://wiki.debian.org/Multiarch/HOWTO

  You would want --add-architecture armhf. I cannot promise anything about how easy this is or how well/if it will work for what you want to do, especially since this is something that needs the GUI stack.

• Get another SD card and try install the 32-bit version of RaspiOS. These are the ones on the download page that aren't marked "64-bit". You could also try the "Legacy" version, which is probably closer to the one that download was built for (on the page it actually says "Raspbian Wheezy", which is nine years old).

  I do not know if this means your memory will be limited to 3 GB, although the Pi 5 will still have a lot more going for it than the models that were current 9 years ago.

I'd recommend trying the second one first as it will be much easier than the first -- all you have to do is create the card, turn it one, and sudo apt install minecraft-pi.

> ./minecraft-pi 
./minecraft-pi: error while loading shared libraries: libGLESv2.so: cannot open shared object file: No such file or directory

That list is abbreviated but you can see there are a few things not found; libSDL is closely related to openGL(ES) and libpng is for .png images.

To check for which package libGLESv2.so is in:

• Try and install a 32-bit userland ("userland" = software besides the kernel, which a 64-bit kernel can run 32-bit executables if all the dependencies are met) inside your 64-bit OS: https://wiki.debian.org/Multiarch/HOWTO

  You would want --add-architecture armhf. I cannot promise anything about how easy this is or how well/if it will work for what you want to do, especially since this is something that needs the GUI stack.

• Get another SD card and try the 32-bit version of RaspiOS. These are the ones on the download page that aren't marked "64-bit". You could also try the "Legacy" version, which is probably closer to the one that download was built for (on the page it actually says "Raspbian Wheezy", which is nine years old).

  I do not know if this means your memory will be limited to 3 GB, although the Pi 5 will still have a lot more going for it than the models that were current 9 years ago.

I'd recommend trying the second one first as it will be much easier than the first -- all you have to do is create the card, turn it on, and sudo apt install minecraft-pi.

Your question hints at the possibility you did try one of these, but unfortunately you could not be bothered to explain this and we cannot read minds, at least over the internet, so there is not much I can say about that.

When I download a file, unzip it and try to run the executable nothing happens.

What file? How did you try and "run the executable"? What can anyone say to this except, "I guess if whatever it is you are talking about doesn't work, it doesn't work, oh well.." There are details you should include in your question if you want help with them.

The duplicate I linked earlier does include a link and detailed information:

Up-to-date java version for setting up a minecraft server on raspberry pi 4

You could follow that procedure, or whatever else you like you find online, but if they do not work and you want help you'll need to include detailed information about exactly what you tried and what happened.

I tried installing Minecraft Pi from the official website, and unzipped the tarball using the terminal. I then located the folder using the cd command and tried to run the Linux executable from there with ./minecraft-pi. I get the error cannot find file when the file is clearly in the directory I am trying to run it from. When I use the ls command to try and see if it is getting recognised by the terminal, it shows everything but the executable. (like images needed for the game, etc)

I did this as well.

> tar -xzf minecraft-pi-0.1.1.tar.gz
> cd mcpi
> ls
api/  CONTROLS.txt  data/  HOW_TO_RUN.txt  LICENSE.txt  minecraft-pi*  VERSION.txt

The file is there and it is executable. Next:

> ./minecraft-pi 
exec: Failed to execute process './minecraft-pi': The file exists and is executable. Check the interpreter or linker?
Press any key to continue...

> file minecraft-pi 
minecraft-pi: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 2.6.26, BuildID[sha1]=ec7c5a7f459230e837d8551aab60b290e9599e63, stripped
Press any key to continue...

The problem here is that this was compiled for 32-bit and I'm using 64-bit. Fortunately, I had a Pi 3 on hand that's still running 32-bit bullseye.

> ./m./minecraft-pi 
./minecraft-pi: error while loading shared libraries: libGLESv2.so: cannot open shared object file: No such file or directory

There's no GUI installed so that makes sense. I checked what libraries it is linked to:

> ldd minecraft-pi    
linux-vdso.so.1 (0x7eff5000)                                                                   
/usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so => /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so (0x76f83000)
libGLESv2.so => not found
libEGL.so => not found                                                                         
libbcm_host.so => /opt/vc/lib/libbcm_host.so (0x76f5c000)
libpng12.so.0 => not found
libSDL-1.2.so.0 => not found
libstdc++.so.6 => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0x76dd4000)
[...]        

That list is abbreviated but you van see there are a few things not found; libSDL is closely related to openGL(ES) and libpng is for .png images.

To check for which packag libGLESv2.so is in:

> apt-file search libGLESv2.so
chromium-browser: /usr/lib/chromium-browser/swiftshader/libGLESv2.so
chromium-common: /usr/lib/chromium/libGLESv2.so
code: /usr/share/code/libGLESv2.so
code-exploration: /usr/share/code-exploration/libGLESv2.so
code-insiders: /usr/share/code-insiders/libGLESv2.so
libgles-dev: /usr/lib/arm-linux-gnueabihf/libGLESv2.so
libgles2: /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2
libgles2: /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.1.0
minecraft-pi: /opt/minecraft-pi/lib/brcm/libGLESv2.so
minecraft-pi: /opt/minecraft-pi/lib/mesa/libGLESv2.so
scratch3: /usr/lib/scratch3/libGLESv2.so
scratch3: /usr/lib/scratch3/swiftshader/libGLESv2.so

If you had a GUI installed, it would have been there already. The interesting thing here is the second last package from the bottom: minecraft-pi.

Presumably, this is because it is only compiled for 32-bit. As I said before, I'm not a minecraft user and eg., the fact that you were looking for the game itself not the server was a bit lost on me.

There are two things you can do here:

• Try and install a 32-bit userland ("userland" = software besides the kernel, which a 64-bit kernel can run 32-bit executables if all the dependencies are me): https://wiki.debian.org/Multiarch/HOWTO

  You would want --add-architecture armhf. I cannot promise anything about how easy this is or how well/if it will work for what you want to do, especially since this is something that needs the GUI stack.

• Get another SD card and try install the 32-bit version of RaspiOS. These are the ones on the download page that aren't marked "64-bit". You could also try the "Legacy" version, which is probably closer to the one that download was built for (on the page it actually says "Raspbian Wheezy", which is nine years old).

  I do not know if this means your memory will be limited to 3 GB, although the Pi 5 will still have a lot more going for it than the models that were current 9 years ago.

I'd recommend trying the second one first as it will be much easier than the first -- all you have to do is create the card, turn it one, and sudo apt install minecraft-pi.

What file? How did you try and "run the executable"? Again, these are details you should include in your question if you want help with them.

What file? How did you try and "run the executable"? What can anyone say to this except, "I guess if whatever it is you are talking about doesn't work, it doesn't work, oh well.." There are details you should include in your question if you want help with them.