Hi all!
I wanted to download Dolphin on my desktop (Ubuntu 18.04, gcc version says gcc version 7.4.0).
I was following this guide: dolphin install guide - linux
using the heading "Ubuntu->16.04 LTS" for dependencies.
I got to step 3, where I successfully cmake'd but failed to make.
Here is the failing output:
I'm not sure what gcc is upset at here, it looks like a fine line of code. In my experience that usually indicates a broken header file inclusion or macro in a previous line above.
Anyway, I was hoping someone in these forums has seen this before and came across a solution.
Thank you!
I wanted to download Dolphin on my desktop (Ubuntu 18.04, gcc version says gcc version 7.4.0).
I was following this guide: dolphin install guide - linux
using the heading "Ubuntu->16.04 LTS" for dependencies.
I got to step 3, where I successfully cmake'd but failed to make.
Here is the failing output:
Code:
[ 26%] Building CXX object Source/Core/VideoBackends/OGL/CMakeFiles/videoogl.dir/RasterFont.cpp.o
In file included from /usr/lib/gcc/x86_64-linux-gnu/7/include-fixed/limits.h:194:0,
from /usr/lib/gcc/x86_64-linux-gnu/7/include-fixed/syslimits.h:7,
from /usr/lib/gcc/x86_64-linux-gnu/7/include-fixed/limits.h:34,
from /home/kyle/Dolphin/dolphin-emu/Build/Source/CMakeFiles/pch.dir/pch.h:35,
from <command-line>:0:
/home/kyle/Dolphin/dolphin-emu/Source/Core/VideoBackends/OGL/RasterFont.cpp:18:18: error: expected unqualified-id before numeric constant
static const int CHAR_WIDTH = 8;
^
Source/Core/VideoBackends/OGL/CMakeFiles/videoogl.dir/build.make:238: recipe for target 'Source/Core/VideoBackends/OGL/CMakeFiles/videoogl.dir/RasterFont.cpp.o' failed
make[2]: *** [Source/Core/VideoBackends/OGL/CMakeFiles/videoogl.dir/RasterFont.cpp.o] Error 1
CMakeFiles/Makefile2:1082: recipe for target 'Source/Core/VideoBackends/OGL/CMakeFiles/videoogl.dir/all' failed
make[1]: *** [Source/Core/VideoBackends/OGL/CMakeFiles/videoogl.dir/all] Error 2
Makefile:162: recipe for target 'all' failed
make: *** [all] Error 2
I'm not sure what gcc is upset at here, it looks like a fine line of code. In my experience that usually indicates a broken header file inclusion or macro in a previous line above.
Anyway, I was hoping someone in these forums has seen this before and came across a solution.
Thank you!