>>> On 20.09.18 at 20:19, wrote:
> I've just encountered this problem, building with the master branch of
> OpenEmbedded and Yocto's poky, with compiler flags that include
> _FORTIFY_SOURCE=2 -msse3
> with gcc 8.2.0.
>
> Xen's x86_emulator header file does:
> #pragma GCC target("no-sse")
On Tue, Sep 4, 2018 at 2:07 AM Jan Beulich wrote:
>
> >>> On 04.09.18 at 09:32, wrote:
> > Am Mon, 03 Sep 2018 06:35:42 -0600
> > schrieb "Jan Beulich" :
> >
> >> what is the actual problem? The mere
> >> listing of compiler flags passed does not make clear to me where the clash
> >> is, or how i
>>> On 04.09.18 at 09:32, wrote:
> Am Mon, 03 Sep 2018 06:35:42 -0600
> schrieb "Jan Beulich" :
>
>> what is the actual problem? The mere
>> listing of compiler flags passed does not make clear to me where the clash
>> is, or how it would surface.
>
> As I noticed just now, it fails to build onl
Am Mon, 03 Sep 2018 06:35:42 -0600
schrieb "Jan Beulich" :
> what is the actual problem? The mere
> listing of compiler flags passed does not make clear to me where the clash
> is, or how it would surface.
As I noticed just now, it fails to build only in Tumbleweed. So in this
specific case osst
>>> On 03.09.18 at 11:53, wrote:
> Since about two months staging fails to build because tools/fuzz can not cope
> with CFLAGS="-O2 -Wall -fstack-protector-strong -funwind-tables
> -fasynchronous-unwind-tables -fstack-clash-protection". While I can easily
> hide the bug by undefining _FORTIFY_
