Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Jun 2022 18:59:36 +0000
From:      bugzilla-noreply@freebsd.org
To:        toolchain@FreeBSD.org
Subject:   [Bug 264949] lang/gcc11: Needs build time warning for /tmp consumption
Message-ID:  <bug-264949-29464-nB99qQzSYl@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-264949-29464@https.bugs.freebsd.org/bugzilla/>
References:  <bug-264949-29464@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264949

Matthias Andree <mandree@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mandree@FreeBSD.org

--- Comment #21 from Matthias Andree <mandree@FreeBSD.org> ---
A few thoughts here:

- should build cluster defaults possibly be refactored to a separate
cluster-specific configuration (that will obviously have to be documented a=
nd
publicly available so we stand a chance of analyzing pkg-fallout mail)

- should there be a tuning guide which gets revisited, say, yearly, from
configuration data we have, or from polling with users, to decide what the
default port settings should look like? Say, "what did people usually buy f=
ive
or four years ago" which should cover most, and those who run written-off s=
tuff
may occasionally tweak. (*)

Or do we need to offer a template file for make.conf with a handful
commented-out sections that we consider as a union cover most end-user
machines?

I know I have had fierce discussions about optimization for
graphics/rawtherapee which is default-tuned for run-time performance and one
user was pissing at me in an egoistic local-optimization style "but I don't
need" and generalizing from there. Arguing based on truly obsolete hardware,
like decade old, and I should not rely on GCC (that was at a time when base
clang was not up to snuff the same way as it is today, but let's leave that
aside), and we will not be able to cater for those in the builders or port
defaults either.


(*) This includes my low-end rental virtual root-access server, too, which =
has
1 Xeon core and 2 GB RAM but I try to avoid building the big stuff. I only =
get
upset when default Python 3 stops building there. ;-)

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264949-29464-nB99qQzSYl>