2018-01-17 17:11 GMT+01:00 Herman van Hazendonk :
> Hi Philippe,
>
> You might want to try to patch your kernel for newer GCC versions. We've
> done that successfully with our 3.4 based kernels. See for example the
> commits we used on our LG Hammerhead (Nexus 5) kernel.
> https://github.com/Halium
On 01/17/2018 05:59 PM, philippe gislard wrote:
We are updating our BSP from Krogoth to Pyro.
We are using a kernel designed and patched specifically for our
hardware (3.10.40) that does not compile with GCC 5.x or GCC6.x.
AFAIK, Pyro is qualified with GCC 5.x and GCC6.x (not with earlier version
Hi Philippe,
You might want to try to patch your kernel for newer GCC versions. We've
done that successfully with our 3.4 based kernels. See for example the
commits we used on our LG Hammerhead (Nexus 5) kernel.
https://github.com/Halium/android_kernel_lge_hammerhead/commits/halium-5.1
See th
Hello,
We are updating our BSP from Krogoth to Pyro.
We are using a kernel designed and patched specifically for our
hardware (3.10.40) that does not compile with GCC 5.x or GCC6.x.
AFAIK, Pyro is qualified with GCC 5.x and GCC6.x (not with earlier versions).
What is the easiest way to use two to
Hello,
We are updating our BSP from Krogoth to Pyro.
We are using a kernel designed and patched specifically for our hardware
(3.10.40) that does not compile with GCC 5.x or GCC6.x.
AFAIK, Pyro is qualified with GCC 5.x and GCC6.x (not with earlier versions).
What is the easiest way to use two t
