Date: Thu, 24 Sep 2020 11:53:25 +0200 From: Niclas Zeising <zeising+freebsd@daemonic.se> To: Stefan Esser <se@freebsd.org>, monochrome <monochrome@twcny.rr.com> Cc: freebsd-current@freebsd.org Subject: Re: geeqie, and neverball build problem on 13-current Message-ID: <c9656eab-bf98-e4b0-89e2-3ff5bbe66b49@daemonic.se> In-Reply-To: <e1f40be6-46b3-a222-501b-4f5b78488358@freebsd.org> References: <59b99301-028c-132a-c974-30608ea18d24@twcny.rr.com> <70e5cb57-c78c-39cc-d7f8-20afbefe00fa@daemonic.se> <e1f40be6-46b3-a222-501b-4f5b78488358@freebsd.org>
index | next in thread | previous in thread | raw e-mail
On 2020-09-24 11:52, Stefan Esser wrote: > Am 24.09.20 um 11:24 schrieb Niclas Zeising: >> On 2020-09-24 11:17, monochrome wrote: >>> Not sure how long this has been a problem, I noticed with the new >>> version of geeqie (geeqie-devel builds fine) and found the neverball >>> problem when rebuilding all packages to investigate. neverball output >>> changes with consecutive build attempts, geeqie does not. >> >> This is related to the update of llvm to 11. With this update, builds >> are by default using -fno-common, which means global variables cannot >> exist in multiple places. gcc 10 has the same default. A quick fix >> is to add -fcommon to CFLAGS, but the proper fix is to update the >> application source to only have the variable in one place. > > This was very easy to fix (like most of the ports affected by the > -fno-common issue). > > The port is updated (r549911) and packages will appear in due time. Great! Thanks for doing the work! Regards -- Niclashelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c9656eab-bf98-e4b0-89e2-3ff5bbe66b49>