On Dec 31, 2014, at 21:20, Garrett Cooper <yaneurab...@gmail.com> wrote:
> On Dec 31, 2014, at 21:12, Garrett Cooper <yaneurab...@gmail.com> wrote:
>
>> On Dec 31, 2014, at 20:44, Garrett Cooper <yaneurab...@gmail.com> wrote:
>>
>>> On Dec 31, 2014, at 20:25, Warner Losh <i...@bsdimp.com> wrote:
>>
>> …
>>
>>>> This change is wrong. bsd.sys.mk was eliminated on purpose, dammit.
>>>
>>> Sorry. Should have asked first. Now the build is broken on all
>>> architectures :/. What next?
>>
>> Also, that code has been in there for over a decade. It seems a bit
>> dangerous to remove it without at least a ports -exp or make tinderbox run…
>
> Hmmm… would it make sense to disable clang warnings from within bsd.sys.mk,
> like we do with sparc64?
> Thanks!
>
> 117 .if ${MACHINE_CPUARCH} == "sparc64"
> 118 # Don't emit .cfi directives, since we must use GNU as on sparc64, for
> now.
> 119 CFLAGS.clang+= -fno-dwarf2-cfi-asm
> 120 .endif # SPARC64
Or just disable -Werror...?
signature.asc
Description: Message signed with OpenPGP using GPGMail
