Date: Sun, 26 Feb 2023 14:42:01 +0100 From: Matthias Andree <matthias.andree@tu-dortmund.de> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: Piotr Kubaj <pkubaj@freebsd.org>, ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: c8c2d4f22536 - main - lang/python3: allow using LTO on powerpc64 Message-ID: <67250c57-fcb7-905a-cacf-8a43ba53156f@tu-dortmund.de> In-Reply-To: <Y/tP6VomDdWJGjhj@FreeBSD.org> References: <202302241548.31OFmQ39049727@gitrepo.freebsd.org> <98e988fa-9c8b-abee-8357-1cacd7462014@tu-dortmund.de> <Y/tP6VomDdWJGjhj@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 26.02.23 um 13:26 schrieb Alexey Dokuchaev:
> On Sun, Feb 26, 2023 at 01:00:19PM +0100, Matthias Andree wrote:
>> Am 24.02.23 um 16:48 schrieb Piotr Kubaj:
>>> commit c8c2d4f2253694802ef720f098c57800570ad2fc
>>>
>>> lang/python3: allow using LTO on powerpc64
>>>
>>> It was recently fixed and will be available in 13.2-RELEASE.
>>> Since LTO is not enabled by default, it's ok to make it available.
>>
>> Careful. LTO causes EXCESSIVE memory use for the build.
>> I've had to disable it for a low-memory server I operate (amd64 based,
>> but that's the LTO feature itself, not the CPU).
>
> I think most people just disable LTO because they don't have 256GB+ or
> whatever amount of RAM it demands for arguably rather little gain.
>
> Putting OPTIONS_UNSET+=LTO in your /etc/make.conf makes the ports tree
> much more usable.
Yeah. I have put my make-fu through the wringer and have ended up with:
OPTIONS_UNSET+=${MAINTAINER:tl:Nmandree@freebsd.org:C/.+/LTO/}
which only disables it on ports that I do not maintain, so I can still
test, for instance, graphics/rawtherapee LTO builds.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?67250c57-fcb7-905a-cacf-8a43ba53156f>