Dinothawr, Raspberry Pi and gcc flags

RetroArch General
#1

Hi there,

I’ve built Dinothawr on the Raspberry Pi, where I run retroarch on an X-less enviroment (dispmanx/EGL GLES context). The game runs great!

However, I usually pass these flags in the Makefile or Makefile.libretro of each core:


CXXFLAGS += -Ofast -mfpu=vfp -mfloat-abi=hard -march=armv6zk -mtune=arm1176jzf-s
CFLAGS += -Ofast -mfpu=vfp -mfloat-abi=hard -march=armv6zk -mtune=arm1176jzf-s

Well, these work great for every core EXCEPT Dinothawr. If I use that when building Dinothawr, the game exits before entering graphics mode, and outputs this message:

“pure virtual method called”
“terminate called without an active exception”

Compiling it in debug mode results on a working executable, so I have no way to debug this any further. So, are these CFLAGS supposed to be a good idea? According to Raspbian developers, they are:

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=66&t=11629

…so I think the game should compile with those (they are the default on my toolchain configuration: I use distcc to outsource the compilation workload since the Pi is too slow for that).

PD: This game is beautiful. The music is amazing! It remembered me of Braid, just not in some Micro$ POS.

#2

That sounds like the compiler flags are breaking the binary. You don’t really need uber-super-mega optimized build for Dinothawr. It should be more than fast enough for Pi.

#3

Yes, of course it’s smooth as silk on the Pi, don’t worry. It’s only that I always try to understand why those things happend, so I can learn while I have fun building programs for the Pi :slight_smile:

Thanks!