| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This is to fix build issues with GCC 7 in QtWebKit and QtIvi.
|
| |
|
|
|
| |
This fixes a deprecation warning in libgdata that occurs after the
Gtk+ upgrade.
|
| | |
|
| |
|
|
|
| |
QtWebKit is only used by the GENIVI Demo Platform; I have no idea
if it's possible for it to use a later version.
|
| |
|
|
| |
This is for faster feedback while fixing the remaining issues.
|
| |
|
|
|
|
|
|
| |
Otherwise you see various link errors like this:
cancel-cancel.o: file not recognized: File truncated
Somehow zero-byte object files are created at random.
|
| |
|
|
|
|
|
| |
WebKit has a bug that causes compile failures with GCC 7:
https://bugs.webkit.org/show_bug.cgi?id=167642
gcrypt upgrade is required to build new WebKit.
|
| |
|
|
|
|
|
|
| |
Hopefully to fix GCC 7 build issue:
/usr/include/QtCore/qmetatype.h:378:12: error: must use '.*' or '->*' to call pointer-to-member function in '_typedThis->QtPrivate::ConverterFunctor<QFlags<QtIVIClimateControl::AirflowDirection>, int, int (QFlags<QtIVIClimateControl::AirflowDirection>::*)() const noexcept>::m_function (...)', e.g. '(... ->* _typedThis->QtPrivate::ConverterFunctor<QFlags<QtIVIClimateControl::AirflowDirection>, int, int (QFlags<QtIVIClimateControl::AirflowDirection>::*)() const noexcept>::m_function) (...)'
*t = _typedThis->m_function(*f);
Makefile:624: recipe for target '.obj/qtiviclimatecontrol.o' failed
|
| |
|
|
| |
This patch actually fixes a bug too!
|
| |
|
|
|
|
|
|
| |
Older ones fail to build with GCC 7 with this error:
kernel/built-in.o: In function `update_wall_time':
(.text+0x667a4): undefined reference to `____ilog2_NaN'
Makefile:968: recipe for target 'vmlinux' failed
|
| |
|
|
| |
Needed for GTK, which in turn is needed for new Clutter GTK
|
| |
|
|
| |
Needed for latest GTK+
|
| |
|
|
| |
This fixes build issues with Clutter with GCC 7.
|
| |
|
|
|
| |
Builds still fail with implicit-fallthrough warnings even with the /*
fall through */ comments in place.
|
| |
|
|
|
| |
They helpfully force -Werror on everyone so we have to backport a couple
of `// FALLTHRU` comments to fix the build...
|
| |
|
|
| |
Patch from https://github.com/openembedded/meta-openembedded/commit/c9f063c218181e4eac3a0a67d74ce91b898a6443
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes a build failure:
In file included from fcmatch.c:287:0:
fcobjs.h:54:3: error: 'PRI_CHAR_WIDTH_STRONG' undeclared here (not in a function); did you mean 'PRI_WIDTH_STRONG'?
FC_OBJECT (CHAR_WIDTH, FcTypeInteger, NULL)
^~~~~~~~~~~~~~~~~~~~~
PRI_WIDTH_STRONG
fcobjs.h:54:26: error: 'PRI_CHAR_WIDTH_WEAK' undeclared here (not in a function); did you mean 'PRI_WIDTH_WEAK'?
FC_OBJECT (CHAR_WIDTH, FcTypeInteger, NULL)
^~~~~~~~~~~~~~~~~~~
PRI_WIDTH_WEAK
|
| |
|
|
| |
Fixes build error with GCC 7
|
| |\
| |
| |
| | |
'origin/staging/jjardon/sam/gcc7.1-bootstrap-fix' into staging/sam/gcc7.1-bootstrap-fix
|
| | | |
|
| | |
| |
| |
| | |
This is needed for the mesa r600 driver
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is how a runner looks like:
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/docker-252:1-262208-36eaa91b86966a7afa39fbdbe717bdec58bc10efc52e09accd3e8e9ee4038658 10G 144M 9.9G 2% /
tmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/vda1 79G 1.2G 75G 2% /cache
shm 64M 0 64M 0% /dev/shm
|
| | | |
|
| | | |
|
| |/
|
|
| |
This is needed for LLVM 4.0
|
| |
|
|
|
| |
Fixes compile failures in Mesa that occur with GCC 7.1. The libdrm
and LLVM updates are required for latest Mesa.
|
| |
|
|
|
|
|
|
|
| |
The 0.10.x series is ancient, and seems to have build
failures with GCC 7.
Upstream has also changed for this project, hence the new repo URL.
Some kind of merging happened that meant the new upstream repo isn't
a simple continuation of the previous one.
|
| |
|
|
|
|
|
| |
We are stuck with SYSLINUX 4.06 due to design flaws in how deployment
works with YBD and Morph. In order to fix compile issues with GCC 7 I
have updated the embedded copy of lzo/ in the SYSLINUX source tree
from the syslinux.git 'master' branch.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This fixes a compile failure with GCC 7:
kernel/built-in.o: In function `update_wall_time':
(.text+0x69744): undefined reference to `____ilog2_NaN'
Makefile:969: recipe for target 'vmlinux' failed
And should generally be harmless.
See also: https://marc.info/?l=linux-kernel&m=147672952517795&w=2
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes a build failure:
amd64-linux-nat.c:497:1: error: conflicting types for 'ps_get_thread_area'
ps_get_thread_area (const struct ps_prochandle *ph,
^~~~~~~~~~~~~~~~~~
In file included from gdb_proc_service.h:25:0,
from amd64-linux-nat.c:50:
/usr/include/proc_service.h:72:17: note: previous declaration of 'ps_get_thread_area' was here
extern ps_err_e ps_get_thread_area (struct ps_prochandle *,
^~~~~~~~~~~~~~~~~~
Makefile:1081: recipe for target 'amd64-linux-nat.o' failed
make[2]: *** [amd64-linux-nat.o] Error 1
|
| |
|
|
|
|
| |
GCC 5.3 fails to build against GLIBC 2.25 due to use of putc() which
triggeres a compile warning. As we seem to build with -Werror this
causes the build to break.
|
| |
|
|
|
|
|
|
|
|
|
| |
This is needed after updating stage2-glibc to 2.25, which in turn was
needed after upgrading GCC.
Fixes issues like this:
/tools/include/limits.h:145:17: error: missing binary operator before token "("
#if __GLIBC_USE (IEC_60559_BFP_EXT)
^
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The GCC version needs to be manually updated in a path name in
libstdc++.morph, I forgot to do that in commit 64813d0134a7796
leading to this issue in stage2-gcc during bootstrap:
x86_64-bootstrap-linux-gnu-g++ --sysroot=/root/ybd/tmp/tmpXB_LVo -fno-PIE -c -DIN_GCC_FRONTEND -g -O2 -DIN_GCC -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -Ic -I../../gcc -I../../gcc/c -I../../gcc/../include -I../../gcc/../libcpp/include -I/root/ybd/tmp/tmpXB_LVo/stage2-gcc.build/o/./gmp -I/root/ybd/tmp/tmpXB_LVo/stage2-gcc.build/gmp -I/root/ybd/tmp/tmpXB_LVo/stage2-gcc.build/o/./mpfr/src -I/root/ybd/tmp/tmpXB_LVo/stage2-gcc.build/mpfr/src -I/root/ybd/tmp/tmpXB_LVo/stage2-gcc.build/mpc/src -I../../gcc/../libdecnumber -I../../gcc/../libdecnumber/bid -I../libdecnumber -I../../gcc/../libbacktrace -o c/c-lang.o -MT c/c-lang.o -MMD -MP -MF c/.deps/c-lang.TPo ../../gcc/c/c-lang.c
In file included from ../../gcc/c/c-lang.c:22:0:
../../gcc/system.h:221:11: fatal error: algorithm: No such file or directory
# include <algorithm>
^~~~~~~~~~~
compilation terminated.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes a build issue with GCC 7.1:
In file included from ../sysdeps/x86_64/fpu/multiarch/e_pow.c:17:0:
../sysdeps/ieee754/dbl-64/e_pow.c: In function 'checkint':
../sysdeps/ieee754/dbl-64/e_pow.c:469:13: error: '<<' in boolean context, did you mean '<' ? [-Werror=int-in-bool-context]
if (n << (k - 20))
~~^~~~~~~~~~~
../sysdeps/ieee754/dbl-64/e_pow.c:471:17: error: '<<' in boolean context, did you mean '<' ? [-Werror=int-in-bool-context]
return (n << (k - 21)) ? -1 : 1;
~~~^~~~~~~~~~~~
../sysdeps/ieee754/dbl-64/e_pow.c:477:9: error: '<<' in boolean context, did you mean '<' ? [-Werror=int-in-bool-context]
if (m << (k + 12))
~~^~~~~~~~~~~
../sysdeps/ieee754/dbl-64/e_pow.c:479:13: error: '<<' in boolean context, did you mean '<' ? [-Werror=int-in-bool-context]
return (m << (k + 11)) ? -1 : 1;
~~~^~~~~~~~~~~~
|
| |
|
|
| |
The ELF ABI version is different on little-endian.
|
