Salastil/ckb-next
1
0
Fork 0
mirror of https://github.com/ckb-next/ckb-next.git synced 2026-10-11 21:07:21 -04:00
Code Issues Packages Projects Releases Wiki Activity

Explicitly request signed char.

Browse Source 
The ckb-daemon code seems to implicitly assume char is signed,
which, while accurate for x86 for performance reasons, is
unspecified by the C standard. This breaks the code on ARM chips
like the Raspberry Pi where char is unsigned by default.

Therefore, explicitly request signed chars to GCC/Clang.
This commit is contained in:
Dan Ravensloft
2017-08-03 16:01:41 +01:00
parent 5c51eaacee
commit 33a9607cf6
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/ckb/ckb.pro
+6
View File
@@ -11,6 +11,12 @@ QMAKE_LIBS_OPENGL =
QMAKE_CFLAGS += -Wno-unused-parameter
QMAKE_CXXFLAGS += -Wno-unused-parameter
# Explicitly require signed char to fix issues on ARM, where char is
# unsigned by default for performance reasons, compared to x86's
# default-signed char.
QMAKE_CFLAGS += -fsigned-char
QMAKE_CXXFLAGS += -fsigned-char
# Output path
macx {
DESTDIR = $$PWD/../..