From nobody Fri Jul 01 11:31:57 2022 X-Original-To: toolchain@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id C8E3A8B017D for ; Fri, 1 Jul 2022 11:31:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LZCht4c6Vz3n3H for ; Fri, 1 Jul 2022 11:31:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 7E8181AC01 for ; Fri, 1 Jul 2022 11:31:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 261BVw74057396 for ; Fri, 1 Jul 2022 11:31:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 261BVwZV057395 for toolchain@FreeBSD.org; Fri, 1 Jul 2022 11:31:58 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 264949] lang/gcc11: Needs build time warning for /tmp consumption Date: Fri, 01 Jul 2022 11:31:57 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: salvadore@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: toolchain@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_file_loc bug_severity bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Maintenance of FreeBSD s integrated toolchain List-Archive: https://lists.freebsd.org/archives/freebsd-toolchain List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-toolchain@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1656675118; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=viXfOIw7ZI91xh1jPsWbz3KeMI076q+8Z64tF5DJysM=; b=gcABnxA9Zm2vJI1PpQLV4bdwd+PbGDPlLaoKD4c2qCrRtGhQbsIgo/N7jaulBCKhEpjIpd BS6WN6ZCJQqhyqzLdiljidgnI08OLPdyenFWekqzBd44Ew0hMWyI3kzTQwezcVwRqzZxNZ 5JDSea3V6X+19O1NMKW0XOY8AeeF+449/RD2RhsYd6NkaViJmRtsXBg+/lMzu2H3bxacjG GicBGeTIw11vuBHaDami8tVCWj1XD8zgRFMjWSHgHINfmDS9q0Ti9sghVu5P5FsExz8b1P fGQF+vB1YMhVEwu9MYmSLdvZhHGsqaJhfSZ9lMMnkGWJfqUnm9Szo8AZH1q4sQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1656675118; a=rsa-sha256; cv=none; b=yFCcJek+GNFhvBuDJN1WtWr1/BispmiuTzJsZILCNSddbTLlk7yNqCC7eE1DhyKAI/9d+F kr+ZZ4deQGGTCV+0xCpSQLXXoJAi8VnqP/l/omAPO5oKd+41/qFoZciRIKqm5blGpWNBrE bal9yFLhRLVRXjeSMGTf3NpBTgg28bDVJ1ec0yaSvkyy/HMDnUCwkW9xbxnGJVpYfe1m7x p4B0UiCLLKKzgsRRE7e9UXhFn4dhV6ApBSaos6HmJ8ydOtIJDXcY2JwVaBwPkZcO5Sxhqe x2mzV0gJJUhmxduAZlBc6bxLtSAqh+81LRyBrrDcSC3p45cNLJzEFGVi8WixYg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264949 Lorenzo Salvadore changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://reviews.freebsd.org | |/D35688 Severity|Affects Only Me |Affects Some People Status|Open |In Progress --- Comment #22 from Lorenzo Salvadore --- I have the impression that I am the only one to be worried about package bu= ild servers load, so I would say that at least for now writing a pkg-help is enough. We can always find a better solution later if needed. I have created a phabricator review with a pkg-help draft: https://reviews.freebsd.org/D35688 (In reply to Mark Millard from comment #18) > And other ports would also be built during those same 8+ > hours: 23 other builders would be available and probably > be active much of the time. If all remaining builders are active, it probably means that the builders making gcc could be used to make something else if compilation was quickier= . On the other hand, if there are some inactive builders, then they are inactive because they have gcc as dependency and then we have a bottleneck. (In reply to Matthias Andree from comment #21) > - should build cluster defaults possibly be refactored to a separate clus= ter-specific configuration (that will obviously have to be documented and p= ublicly available so we stand a chance of analyzing pkg-fallout mail) I think it is a good idea, but I don't see it happening: it would make maintainance and testing more complex for too little gain. Do we have other cases where default options are good for package build servers but often bad for users building their own ports? (By often, I mean often enough to have reports of users failing their compilations. In this case we have this PR a= nd some more cases on EFNet.) > - 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-o= ff stuff may occasionally tweak. We have plenty of different ports, each one with their specific particular cases. I think we can have some general guidelines, as we already have, but= I think choosing the best combination of default options is the maintainer's responsibility. --=20 You are receiving this mail because: You are the assignee for the bug.=