Re: 11-CURRENT build fail with base gcc

On 08/20/2015 14:21, Warner Losh wrote: > >> On Aug 20, 2015, at 10:32 AM, Dimitry Andric wrote: >> >> Ah, this should be replaced with the recently introduced CFLAGS_NO_SIMD >> variable, then? > > Perhaps. Didn’t know this was a thing. That could use useful many places, > though > there were t

Re: 11-CURRENT build fail with base gcc

> On Aug 20, 2015, at 1:21 PM, Warner Losh wrote: > > >> On Aug 20, 2015, at 10:32 AM, Dimitry Andric wrote: >> >> On 20 Aug 2015, at 18:24, Warner Losh wrote: >>> On Aug 20, 2015, at 9:38 AM, Oliver Pinter wrote: >> ... >>> >>> I think you are wrong about the cause. -mno-avx i

Re: 11-CURRENT build fail with base gcc

> On Aug 20, 2015, at 10:32 AM, Dimitry Andric wrote: > > On 20 Aug 2015, at 18:24, Warner Losh wrote: >> >>> On Aug 20, 2015, at 9:38 AM, Oliver Pinter >>> wrote: > ... >> >> I think you are wrong about the cause. -mno-avx is bogusly listed >> unconditionally >> in efi/Makefile.inc. I’m w

Re: 11-CURRENT build fail with base gcc

On 08/20/2015 11:32, Dimitry Andric wrote: > On 20 Aug 2015, at 18:24, Warner Losh wrote: >> >> I think you are wrong about the cause. -mno-avx is bogusly listed >> unconditionally >> in efi/Makefile.inc. I’m working on a patch now… > > Ah, this should be replaced with the recently introduced CF

Re: 11-CURRENT build fail with base gcc

On 20 Aug 2015, at 18:24, Warner Losh wrote: > >> On Aug 20, 2015, at 9:38 AM, Oliver Pinter >> wrote: ... > > I think you are wrong about the cause. -mno-avx is bogusly listed > unconditionally > in efi/Makefile.inc. I’m working on a patch now… Ah, this should be replaced with the recently

Re: 11-CURRENT build fail with base gcc

On 8/20/15, Warner Losh wrote: > >> On Aug 20, 2015, at 9:38 AM, Oliver Pinter >> wrote: >> >> On 8/20/15, Dimitry Andric wrote: >>> On 20 Aug 2015, at 00:56, Oliver Pinter >>> wrote: I got this error, when I try to build recent 11-CURRENT with gcc on amd64 box: --- del

Re: 11-CURRENT build fail with base gcc

> On Aug 20, 2015, at 9:38 AM, Oliver Pinter > wrote: > > On 8/20/15, Dimitry Andric wrote: >> On 20 Aug 2015, at 00:56, Oliver Pinter >> wrote: >>> I got this error, when I try to build recent 11-CURRENT with gcc on amd64 >>> box: >>> >>> --- delay.o --- >>> cc -O2 -pipe -fPIC -mno-red-

Re: 11-CURRENT build fail with base gcc

On 8/20/15, Dimitry Andric wrote: > On 20 Aug 2015, at 00:56, Oliver Pinter > wrote: >> I got this error, when I try to build recent 11-CURRENT with gcc on amd64 >> box: >> >> --- delay.o --- >> cc -O2 -pipe -fPIC -mno-red-zone >> -I/usr/data/source/git/opBSD/opBSD.git/sys/boot/efi/libefi/../

Re: 11-CURRENT build fail with base gcc

On 20 Aug 2015, at 00:56, Oliver Pinter wrote: > I got this error, when I try to build recent 11-CURRENT with gcc on amd64 box: > > --- delay.o --- > cc -O2 -pipe -fPIC -mno-red-zone > -I/usr/data/source/git/opBSD/opBSD.git/sys/boot/efi/libefi/../include > -I/usr/data/source/git/opBSD/opBSD.g

Re: 11-CURRENT build fail with base gcc

> On Aug 19, 2015, at 8:36 PM, Julian Elischer wrote: > > On 8/20/15 6:56 AM, Oliver Pinter wrote: >> Hi All! >> >> I got this error, when I try to build recent 11-CURRENT with gcc on amd64 >> box: > > I thought that the switch do only allow clang had already been thrown… Not even close. Cla

Re: 11-CURRENT build fail with base gcc

On 8/20/15 6:56 AM, Oliver Pinter wrote: Hi All! I got this error, when I try to build recent 11-CURRENT with gcc on amd64 box: I thought that the switch do only allow clang had already been thrown... --- delay.o --- cc -O2 -pipe -fPIC -mno-red-zone -I/usr/data/source/git/opBSD/opBSD.gi

11-CURRENT build fail with base gcc

Hi All! I got this error, when I try to build recent 11-CURRENT with gcc on amd64 box: --- delay.o --- cc -O2 -pipe -fPIC -mno-red-zone -I/usr/data/source/git/opBSD/opBSD.git/sys/boot/efi/libefi/../include -I/usr/data/source/git/opBSD/opBSD.git/sys/boot/efi/libefi/../include/amd64 -I/usr/data