Date: Wed, 16 Oct 2019 08:56:31 +0200 (CEST) From: Gerald Pfeifer <gerald@pfeifer.com> To: Rodrigo Osorio <rodrigo@FreeBSD.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r514406 - in head/security: . libscep libscep/files p5-Crypt-LibSCEP Message-ID: <alpine.LSU.2.21.1910160842130.3728@anthias.pfeifer.com> In-Reply-To: <201910131602.x9DG21iY069347@repo.freebsd.org> References: <201910131602.x9DG21iY069347@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 13 Oct 2019, Rodrigo Osorio wrote: > Author: rodrigo > Date: Sun Oct 13 16:02:00 2019 > New Revision: 514406 > URL: https://svnweb.freebsd.org/changeset/ports/514406 > Added: head/security/libscep/Makefile > ============================================================================== > +USE_GCC= yes This... > Added: head/security/p5-Crypt-LibSCEP/Makefile > ============================================================================== > +USE_GCC= yes ...and this make me a little uneasy. Why does a new port / current software require GCC? Does it really not work with clang? (That may be worth a comment in the Makefiles.) Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LSU.2.21.1910160842130.3728>