On Sun, 29 Sep 2019, Christos Zoulas wrote:
Sure, but the question is why are you getting errors in the first place.
They should have been downgraded to warnings by -Wno-error-foo.
Something in /etc/mk.conf perhaps?
christos
On Sep 29, 2019, at 3:18 AM, Greywolf wrote:
On Sat, Sep 28,
Sure, but the question is why are you getting errors in the first place.
They should have been downgraded to warnings by -Wno-error-foo.
christos
> On Sep 29, 2019, at 3:18 AM, Greywolf wrote:
>
> On Sat, Sep 28, 2019 at 3:48 AM Christos Zoulas wrote:
>
>> We've chosen not to fix the
> ../../../../external/bsd/drm2/dist/drm/i915/intel_ddi.c -o intel_ddi.o
makeoptions i915drmkms "CWARNFLAGS.intel_ddi.c"+="${${ACTIVE_CC} ==
gcc && ${HAVE_GCC:U0} == 7:? -Wno-error=implicit-fallthrough :}"
this is missing from your build some how.
do you have HAVE_GCC set to something
On Sat, Sep 28, 2019 at 3:48 AM Christos Zoulas wrote:
> We've chosen not to fix the fallthrough warnings in 3rd party code, but
> we instead have changed the default setting to not produce errors. Have
> you made any changes to the compilation environment that caused those to
> become errors
In article ,
Greywolf wrote:
>Sources from 2019-09-26, building a kernel, I get this:
>
>###
>gcc -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -mno-avx
>-msoft-float -mindirect-branch=thunk-inline -mindirect-branch-register
>-ffreestanding -fno-zero-initialized-in-bss
Sources from 2019-09-26, building a kernel, I get this:
###
gcc -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -mno-avx
-msoft-float -mindirect-branch=thunk-inline -mindirect-branch-register
-ffreestanding -fno-zero-initialized-in-bss
-fno-delete-null-pointer-checks -g -O2
