Experimentally tweak debuginfo generation settings some more
Note this is expected to cause the size of the debuginfo packages to balloon, but it's better than not being able to update the package at all. See: https://pagure.io/fedora-infrastructure/issue/11000
This commit is contained in:
parent
62a930c5c3
commit
e6d2a00c82
@ -296,18 +296,17 @@ files for developing applications that use JavaScript engine from webkit2gtk-4.0
|
||||
|
||||
%build
|
||||
# Increase the DIE limit so our debuginfo packages can be size-optimized.
|
||||
# Decreases the size for x86_64 from ~5G to ~1.1G.
|
||||
# Decreases the size for x86_64 from ~5G to ~1.1G. This requires lots of
|
||||
# RAM on the builders, so only do this for x86_64 because other architectures
|
||||
# have underpowered builders that cannot handle a higher limit.
|
||||
# https://bugzilla.redhat.com/show_bug.cgi?id=1456261
|
||||
%global _dwz_max_die_limit 250000000
|
||||
|
||||
# On x86_64, the _dwz_max_die_limit is overridden by the arch-specific limit
|
||||
# from redhat-rpm-config.
|
||||
%global _dwz_max_die_limit_x86_64 250000000
|
||||
|
||||
# Require 8 GB of RAM per vCPU for debuginfo processing
|
||||
%global _find_debuginfo_opts %limit_build -m 8192
|
||||
# Require 16 GB of RAM per vCPU for debuginfo processing.
|
||||
%global _find_debuginfo_opts %limit_build -m 16384
|
||||
|
||||
# Remove debuginfo from 32-bit builds to reduce memory consumption:
|
||||
# Remove debuginfo from 32-bit builds to reduce memory consumption even more.
|
||||
# No amount of optimizing is going to work here.
|
||||
# https://bugs.webkit.org/show_bug.cgi?id=140176
|
||||
# https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/I6IVNA52TXTBRQLKW45CJ5K4RA4WNGMI/
|
||||
%ifarch %{ix86}
|
||||
|
Loading…
Reference in New Issue
Block a user