Hi Mike,
On Wed, Nov 20, 2019 at 09:06:08PM +1300, Paul Eggleton wrote:
> Hi Mike
>
> On Wednesday, 20 November 2019 9:00:10 PM NZDT Mike Looijmans wrote:
> > I ran into this issue yesterday, and this patch solves the compilation on
> > warrior. However, it's a patch for Qt itself, and not for O
Hi Mike
On Wednesday, 20 November 2019 9:00:10 PM NZDT Mike Looijmans wrote:
> I ran into this issue yesterday, and this patch solves the compilation on
> warrior. However, it's a patch for Qt itself, and not for OE.
>
> Is there already a warrior patch in the making, or should I submit one?
Qu
I ran into this issue yesterday, and this patch solves the compilation on
warrior. However, it's a patch for Qt itself, and not for OE.
Is there already a warrior patch in the making, or should I submit one?
On 19-11-19 13:37, Quentin Schulz wrote:
> At least since gcc v8, source code with asm
At least since gcc v8, source code with asm volatile won't compile
anymore.
The volatile qualifier anyway is a no-op since asm blocks are implicitly
volatile as written in the documentation[1].
Let's get rid of this redundant qualifier so we can build with newer
GCCs.
The resulting error message
