Date: Thu, 21 Apr 2022 10:02:11 +0200 From: Evilham <contact@evilham.com> To: freebsd-current@freebsd.org Subject: Re: 'set but unused' breaks drm-*-kmod Message-ID: <43a186ff09129eac264090e12204fa857d9a@yggdrasil.evilham.com> In-Reply-To: <20220421094236.3f023ac540666c140c04f884@bidouilliste.com> References: <263e16c4-0634-88e6-9652-50d0874f027e@protected-networks.net> <20220421094236.3f023ac540666c140c04f884@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On dj., abr. 21 2022, Emmanuel Vadot wrote: > Hello Michael, > > On Wed, 20 Apr 2022 23:39:12 -0400 > Michael Butler <imb@protected-networks.net> wrote: > >> Seems this new requirement breaks kmod builds too .. >> >> The first of many errors was (I stopped chasing them all for >> lack of >> time) .. >> >> --- amdgpu_cs.o --- >> /usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.7.19_3/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c:1210:26: >> error: variable 'priority' set but not used >> [-Werror,-Wunused-but-set-variable] >> enum drm_sched_priority priority; >> ^ >> 1 error generated. >> *** [amdgpu_cs.o] Error code 1 >> > > How are you building the port, directly or with PORTS_MODULES ? > I do make passes on the warning for drm and I did for > set-but-not-used > case but unfortunately this option doesn't exists in 13.0 so I > couldn't > apply those in every branch. > > Cheers, Can confirm the breakage on 14-CURRENT building graphics/drm-devel-kmod in poudriere with matching sources and kernel. Probably due to 8b83d7e0ee54416b0ee58bd85f9c0ae7fb3357a1 -- Evilham
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43a186ff09129eac264090e12204fa857d9a>