0UT1S's

lib/rpm/macros.d/

By Order of Mr.0UT1S

N/A

macros.alt-python310

2.01 KB

macros.alt-python311

2.01 KB

macros.alt-python312

2.01 KB

macros.alt-python313

2.01 KB

macros.alt-python38

1.97 KB

macros.alt-python39

1.98 KB

1.76 KB

macros.efi-srpm

3.00 KB

macros.environment-modules

75 bytes

macros.fedora-misc

2.76 KB

macros.fedora-misc-srpm

239 bytes

macros.firewalld

239 bytes

12.43 KB

macros.ghc-srpm

414 bytes

7.17 KB

390 bytes

macros.kernel-srpm

116 bytes

macros.ldc-srpm

73 bytes

macros.ldconfig

307 bytes

macros.mono-srpm

181 bytes

macros.nodejs-srpm

324 bytes

macros.ocaml-srpm

737 bytes

macros.openblas-srpm

104 bytes

5.06 KB

macros.perl-srpm

794 bytes

macros.pybytecompile

886 bytes

3.36 KB

macros.python-srpm

5.95 KB

1.82 KB

3.63 KB

macros.qt5-qtbase

78 bytes

1001 bytes

macros.rust-srpm

61 bytes

13.53 KB

macros.selinux-policy

6.61 KB

4.03 KB

macros.systemtap

206 bytes

macros.valgrind-srpm

127 bytes

40 bytes

228 bytes

# Macros for reducing debug info size using dwz(1) utility.

# The two default values below should result in dwz taking at most
# 3GB of RAM or so on 64-bit hosts and 2.5GB on 32-bit hosts
# on the largest *.debug files  (in mid 2012 those are
# libreoffice-debuginfo, debuginfos containing
# libxul.so.debug and libwebkitgtk-*.so.*.debug).
# This needs to be tuned based on the amount of available RAM
# on build boxes for each architecture as well as virtual address
# space limitations if dwz is 32-bit program.  While it needs less
# memory than 64-bit program because pointers are smaller, it can
# never have more than 4GB-epsilon of RAM and on some architecture
# even less than that (e.g. 2GB).

# Number of debugging information entries (DIEs) above which
# dwz will stop considering file for multifile optimizations
# and enter a low memory mode, in which it will optimize
# in about half the memory needed otherwise.
%_dwz_low_mem_die_limit		 10000000
# Number of DIEs above which dwz will stop processing
# a file altogether.
%_dwz_max_die_limit     	 50000000

# On x86_64 increase the higher limit to make libwebkit* optimizable.
# libwebkit* in mid 2012 contains roughly 87mil DIEs, and 64-bit
# dwz is able to optimize it from ~1.1GB to ~410MB using 5.2GB of RAM.
%_dwz_max_die_limit_x86_64	110000000

# On ARM, build boxes often have only 512MB of RAM and are very slow.
# Lower both the limits.
%_dwz_low_mem_die_limit_armv5tel  4000000
%_dwz_low_mem_die_limit_armv7hl	  4000000
%_dwz_max_die_limit_armv5tel	 10000000
%_dwz_max_die_limit_armv7hl	 10000000

%_dwz_limit() %{expand:%%{?%{1}_%{_arch}}%%{!?%{1}_%{_arch}:%%%{1}}}
%_find_debuginfo_dwz_opts --run-dwz\\\
   --dwz-low-mem-die-limit %{_dwz_limit _dwz_low_mem_die_limit}\\\
   --dwz-max-die-limit %{_dwz_limit _dwz_max_die_limit}