On Wed, Mar 15 2023 at 02:46:21 PM -04:00:00, Daniel Richard G.
<sk...@iskunk.org> wrote:
Package: chromium
Version: 111.0.5563.64-1
Severity: minor
I've been experimenting with building the latest Debian chromium
package
on Ubuntu 22.04, and in the course of that have found a couple of
minor
issues in the debian/rules file:
* The flags added by optimize=+lto in DEB_BUILD_MAINT_OPTIONS will
cause every compile invocation to print "optimization flag
'-ffat-lto-objects' is not supported" warnings (as the dpkg LTO
flags
are meant for GCC, not Clang), and balloon the RAM required for the
final link from ~2.5 GB to ~30 GB. The link will also require much
more time to complete; on my fairly beefy test system, it went from
under a minute to four hours.
Disabling this explicitly before Debian enables LTO system-wide
would
be a good move, in my view. On Ubuntu, LTO is already the default,
and
without adding this bit, the package is difficult to build in their
infrastructure due to the resource requirements.
Is Ubuntu looking to switch to using Debian's chromium instead of the
snap or flatpak or whatever they currently use?
If that's a "yes", and you're the one working on it, I'd suggest
joining Debian's chromium team. :)
* LDFLAGS is set without obtaining an initial value from
dpkg-buildflags(1).
The attached patch addresses both issues.
Thanks! I'll apply the patch (though I'm not sure yet if we want more
verbose linker output, build logs are already pretty big).
Side note: You may want to consider enabling ThinLTO, by setting
use_thin_lto=true and unsetting concurrent_links. The final link
requires only ~10.5 GB RAM, and completes within minutes.
I'm not clear on how that affects runtime performance; any ideas? I'd
also have to make sure that it works okay on clang-13 (which is what
bullseye is building with).
