Date: Tue, 6 Oct 2020 08:00:45 +0300 (EEST) From: Gerald Pfeifer <gerald@pfeifer.com> To: Piotr Kubaj <pkubaj@FreeBSD.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r551539 - head/devel/libffcall Message-ID: <alpine.LSU.2.23.453.2010060759010.6436@naga> In-Reply-To: <202010051912.095JCL9k036435@repo.freebsd.org> References: <202010051912.095JCL9k036435@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 Oct 2020, Piotr Kubaj wrote: > Log: > devel/libffcall: fix build > > Submitted by: se@ > Reported by: linimon@ > > Modified: > head/devel/libffcall/Makefile > > Modified: head/devel/libffcall/Makefile > ============================================================================== > --- head/devel/libffcall/Makefile Mon Oct 5 19:11:21 2020 (r551538) > +++ head/devel/libffcall/Makefile Mon Oct 5 19:12:21 2020 (r551539) > @@ -19,6 +19,7 @@ BROKEN_mips64= fails to build: gmake[2]: No rule to m > > GNU_CONFIGURE= yes > USES= gmake libtool > +USE_GCC= yes What was the actual failure? I hope not an -fcommon issue, or this would actively block moving the default for USE_GCC from GCC 9 to GCC 10. When introducing USE_GCC these days, it would be good to note (in a comment or the commit message) why. Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LSU.2.23.453.2010060759010.6436>