Page MenuHomeFreeBSD

lang/gcc>=11: Warn about LTO_BOOTSTRAP
ClosedPublic

Authored by salvadore on Jul 1 2022, 11:01 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Dec 7, 10:03 PM
Unknown Object (File)
Sun, Dec 1, 3:04 PM
Unknown Object (File)
Nov 21 2024, 3:21 PM
Unknown Object (File)
Nov 21 2024, 10:20 AM
Unknown Object (File)
Nov 9 2024, 10:02 PM
Unknown Object (File)
Oct 16 2024, 1:20 PM
Unknown Object (File)
Oct 1 2024, 1:14 AM
Unknown Object (File)
Sep 24 2024, 8:39 AM
Subscribers

Details

Summary

Warn users about the amount of ram and time needed to build GCC with
LTO_BOOTSTRP enabled.

PR: 264949
Reported by: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> and others

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Thank you for thinking of our users impacted negatively, Lorenzo.

I think this is the minimum we can do and only suggest tweaking the message a little (breaking the long sentence and one or two style changes) and, for now, only applying this to the "production" ports, that is, skipping the -devel ports (though the latter is more an intuition which you are welcome to ignore).

lang/gcc12/pkg-help
4

How about a minor variation along the lines of:

Building this port with LTO_BOOTSTRAP enabled requires significant amounts of memory and time. Consider disabling LTO_BOOTSTRAP in favor of STANDARD_BOOTSTRAP (or disabling BOOTSTRAP altogether) in case that is a problem.

This revision is now accepted and ready to land.Jul 6 2022, 8:47 PM
This revision was automatically updated to reflect the committed changes.

Thanks Gerald, I have committed the message in the form you suggested. I have committed it both in production and development ports: while I trust your intuition, I really do not see how an additional warning could be problematic, it seems to me that it has only advantages. On the other hand, more differences we have in our gcc ports, more complexity we add to their maintainance.