g++ -Wall -fexceptions -g -Iinclude -I/home/pelu/Escritorio/dungeon/src -c /home/pelu/Escritorio/dungeon/src/GameMap.cpp -o obj/Debug/src/GameMap.o
execvp(./home/pelu/Fundamentos, de, , g++ -Wall -fexceptions -g -Iinclude -I/home/pelu/Escritorio/dungeon/src -c /home/pelu/Escritorio/dungeon/src/GameMap.cpp -o obj/Debug/src/GameMap.o) failed with error 2!
It looks like these two lines are created by actually one call to the compiler, most probably CodeBlocks "pretty-prints" the first line and the second line is the actual
execvp call that CodeBlocks tries to execute. The first parameter of that call is the path to the executable and this one seems to be corrupted.
The Fundamentos folder is named "Fundamentos\ de\ Programación/"
This looks like this is the path that the
execvp call gets passed in, with spaces and non-ASCII letters and this seems to get wrongly inserted into the
execvp call. I don't know how CodeBlocks constructs the compiler call but i would guess this path must be specified somewhere in the toolchain settings of the compiler configuration and im pretty sure this is not the path where gcc is installed. At first i would look there and correct that path (should be
/usr/bin or something like that). If it's not part of the toolchain settings then hopefully someone else with more knowledge about CodeBlocks internals know which other locations contribute to the creation of the compiler call command.