Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Feb 2021 16:55:13 -0700
From:      Rebecca Cran <rebecca@bsdio.com>
To:        Gerald Pfeifer <gerald@pfeifer.com>, Jan Beich <jbeich@FreeBSD.org>, Rebecca Cran <bcran@freebsd.org>
Cc:        ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org
Subject:   Re: svn commit: r511727 - head/sysutils/uefi-edk2-qemu
Message-ID:  <1e3be017-8a27-7a20-3340-2ebc035e2ff7@bsdio.com>
In-Reply-To: <704b6093-69e0-57aa-c56b-33b558dd32ad@pfeifer.com>
References:  <201909100151.x8A1pqC5086268@repo.freebsd.org> <sgp4-x2ho-wny@FreeBSD.org> <1746825a-d196-9390-6c71-45918862e985@freebsd.org> <k1af-wvcl-wny@FreeBSD.org> <704b6093-69e0-57aa-c56b-33b558dd32ad@pfeifer.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2/13/21 3:47 PM, Gerald Pfeifer wrote:
> On Wed, 11 Sep 2019, Jan Beich wrote:
>> Rebecca Cran <bcran@freebsd.org> writes:
>>>> Only lang/gcc (meta port) installs "gcc" symlink. Why not keep USE_GCC
>>>> while using the same hack as sysutils/uefi-edk2-bhyve or misc/seabios?
>>> Oh, I see the problem. It should be
>>> gcc${GCC_DEFAULT}:lang/gcc${GCC_DEFAULT}.
>>>
>>> I'm not sure what hack you're referring to: how do those ports avoid
>>> pulling in gcc as a dependency while still using USE_GCC?
>> USE_GCC=	yes
>> ...
>> .include <bsd.port.mk>
>> RUN_DEPENDS:=	${RUN_DEPENDS:Ngcc*}
> 
> Even better -- and I am sorry it took me so long to get this into the
> ports infrastructure (Mk/bsd.gcc.mk) -- should be a simple
> 
>    USE_GCC=yes:build
> 
> This essentially is a variation of what Jan proposed, just with the
> new ":build" parameter instead of manipulating RUN_DEPENDS directly.
> 
> Okay to commit?

Yes, please do.

-- 
Rebecca Cran




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1e3be017-8a27-7a20-3340-2ebc035e2ff7>