| View previous topic :: View next topic |
| Author |
Message |
motig
n00b
Joined: 11 Oct 2016
Posts: 44
|
 Posted: Thu Apr 17, 2025 10:04 am Post subject: chromium-135.0.7049.84 build.log size [SOLVED] |
 |
|
Greetings,
I have been building www-client/chromium-135.0.7049.84 since yesterday. The build process itself was finished an hour and a half ago and since then emerge has been running grep, sed and other commands on the build log. The build log in question has 89 GB. I don't remember the previous versions of chromium having problems like this (but maybe I was just not present at the machine when this was going on). What is going on with this build log text processing?
One example of a command being run:
| Code: |
root 19357 19355 19 2693 3112 6 11:51 pts/4 00:01:32 grep -E -a warning: .*will.*\[-Wstrict-aliasing\]|warning: .*does.*\[-Wstrict-aliasing\]|warning: .*\[-Wrestrict\]|warning: .*\[-Wundefined-reinterpret-cast\]|warning: .*\[-Wimplicit-function-declaration\]|warning: .*incompatible implicit declaration of built-in function|warning: .*\[-Wbuiltin-declaration-mismatch\]|warning: .*\[-Wuninitialized\]|warning: .*mathematical meaning*\[-Wparentheses\]|warning: .*\[-Wnonnull\]|warning: .*\[-Warray-bounds\]|warning: .*\[-Wfree-nonheap-object\]|warning: .*will always overflow destination buffer|warning: .*\[-Wfortify-source\]|warning: .*assuming pointer wraparound does not occur|warning: .*escape sequence out of range|warning: .*\[-Wstrlcpy-strlcat-size\]|warning: .*\[-Wstrncat-size\]|warning: .*\[-Wsuspicious-bzero\]|warning: .*\[-Wvarargs\]|warning: .*left.*comma.*\[-Wunused-value\]|warning: .*\[-Wconversion-null\]|warning: .*NULL.*\[-Wpointer-arith\]|warning: .*function.*\[-Wpointer-arith\]|warning: .*too few arguments for format|warning: .*missing sentinel in function call.*\[-Wformat=\]|warning: .*\[-Wformat-truncation\]|warning: .*matching.*\[-Wformat=\]|warning: .*\[-Wreturn-type\]|warning: .*\[-Wsizeof-pointer-memaccess\]|warning: .*\[-Waggressive-loop-optimizations\]|warning: .*\[-Wincompatible-pointer-types\]|warning: .*\[-Wincompatible-function-pointer-types\]|warning: .*\[-Wcast-function-type-strict\]|warning: .*\[-Wmismatched-dealloc\]|warning: .*\[-Wclobbered\]|warning: .*\[-Wlto-type-mismatch\]|warning: .*\[-Wodr\]|warning: .*\[-Wargument-undefined-behaviour\]|warning: .*\[-Wmain\]|warning: .*\[-Wimplicit-int\]|warning: .*\[-Wstring-compare\]
|
Not only this takes an extremely long time but having a 90 GB log file written every time I compile this takes a toll on the SSD. I suppose it is not possible to disable writing of this build.log file on disk?
Thank you for any recommendations.
Last edited by motig on Fri Apr 18, 2025 4:07 pm; edited 1 time in total |
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23322
|
| Posted: Thu Apr 17, 2025 1:31 pm Post subject: |
|
|
I cannot comment on the appropriateness of an 89 GB log file, but that does seem ridiculous to me. I don't know if that is standard for Chromium. I know Chromium is itself rather ridiculous in size.
The text processing you cite is scanning the log for messages from the compiler that, if present, indicate poor quality code which may cause problems later, despite building successfully. From reading the Portage code, I think you could define a local override that would avoid running this check, though I cannot recommend doing so, particularly since the naive override would disable the check for all packages, so you would need to do extra work to re-enable it for other packages.
The build.log should be written to a configurable directory, which you could redirect to a spinning drive or a tmpfs, if you have enough RAM. I recognize asking to put an 89 GB log file in RAM is a bit much. Are you using compiler flags or Portage options that increase verbosity? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 55158
Location: 56N 3W
|
| Posted: Thu Apr 17, 2025 1:55 pm Post subject: |
|
|
motig,
That 89G log looks to be excessive, even for chromium.
My build log on a Pi5 is about 220MB.
What does | Code: | | emerge --info chromium |
have to say?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
motig
n00b
Joined: 11 Oct 2016
Posts: 44
|
| Posted: Thu Apr 17, 2025 5:15 pm Post subject: |
|
|
Thank you for the suggestions. It is not a bad idea to connect a spinning drive via USB and redirect the log there. I am not sure though if PORTAGE_LOGDIR redirects the build.log files or if it just creates copies in the specified directory.
Here's the output of "emerge --info chromium":
| Code: |
Portage 3.0.67 (python 3.12.10-final-0, default/linux/amd64/23.0/split-usr/desktop/plasma, gcc-14, glibc-2.40-r8, 6.12.16-gr x86_64)
=================================================================
System Settings
=================================================================
System uname: Linux-6.12.16-gr-x86_64-AMD_Ryzen_7_PRO_4750U_with_Radeon_Graphics-with-glibc2.40
KiB Mem: 32182560 total, 19300052 free
KiB Swap: 4194300 total, 3629804 free
Timestamp of repository gentoo: Sat, 12 Apr 2025 01:45:00 +0000
Head commit of repository gentoo: 243c8ce73ed8f9f1aa01b47af4f53b724338ae44
Timestamp of repository vapoursynth: Tue, 15 Apr 2025 14:37:34 +0000
Head commit of repository vapoursynth: 4e5309f473efe7ba4b3d0387061ea1b56ccd30dd
sh bash 5.2_p37
ld GNU ld (Gentoo 2.44 p1) 2.44.0
app-misc/pax-utils: 1.3.8::gentoo
app-shells/bash: 5.2_p37::gentoo
dev-build/autoconf: 2.13-r8::gentoo, 2.72-r1::gentoo
dev-build/automake: 1.16.5-r2::gentoo, 1.17-r1::gentoo
dev-build/cmake: 3.31.5::gentoo
dev-build/libtool: 2.5.4::gentoo
dev-build/make: 4.4.1-r100::gentoo
dev-build/meson: 1.7.0::gentoo
dev-java/java-config: 2.3.4::gentoo
dev-lang/perl: 5.40.0-r1::gentoo
dev-lang/python: 3.11.9-r1::gentoo, 3.12.10::gentoo, 3.13.3::gentoo
dev-lang/rust: 1.84.1-r1::gentoo
llvm-core/clang: 19.1.7::gentoo
llvm-core/lld: 19.1.7::gentoo
llvm-core/llvm: 19.1.7::gentoo
sys-apps/baselayout: 2.17::gentoo
sys-apps/openrc: 0.56::gentoo
sys-apps/sandbox: 2.39::gentoo
sys-devel/binutils: 2.43-r2::gentoo, 2.44::gentoo
sys-devel/binutils-config: 5.5.2::gentoo
sys-devel/gcc: 14.2.1_p20241221::gentoo
sys-devel/gcc-config: 2.12.1::gentoo
sys-kernel/linux-headers: 6.12::gentoo (virtual/os-headers)
sys-libs/glibc: 2.40-r8::gentoo
Repositories:
gentoo
location: /usr/portage
sync-type: rsync
sync-uri: rsync://lithium.l/gentoo-portage
priority: -1000
volatile: True
sync-rsync-verify-max-age: 3
sync-rsync-verify-metamanifest: no
sync-rsync-verify-jobs: 1
sync-rsync-extra-opts:
customlocal
location: /home/chloe/Downloads/Gentoo/Overlay
masters: gentoo
priority: 0
volatile: True
vapoursynth
location: /var/db/repos/vapoursynth
sync-type: git
sync-uri: https://github.com/gentoo-mirror/vapoursynth.git
masters: gentoo
volatile: False
Binary Repositories:
binhost
priority: 9999
sync-uri: https://mirror.dkm.cz/gentoo/releases/amd64/binpackages/23.0/x86-64-v3
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="@FREE"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe -march=znver2 -mtune=znver2 -funroll-loops -fomit-frame-pointer"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/lib64/libreoffice/program/sofficerc /usr/share/config /usr/share/gnupg/qualified.txt /var/bind"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-O2 -pipe -march=znver2 -mtune=znver2 -funroll-loops -fomit-frame-pointer"
DISTDIR="/mnt/Distfiles"
EMERGE_DEFAULT_OPTS="--quiet-build=y --getbinpkg"
ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GDK_PIXBUF_MODULE_FILE GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR XDG_STATE_HOME"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs binpkg-request-signature buildpkg-live config-protect-if-modified distlocks ebuild-locks fixlafiles icecream ipc-sandbox merge-sync merge-wait multilib-strict news parallel-fetch pid-sandbox pkgdir-index-trusted preserve-libs protect-owned qa-unresolved-soname-deps sandbox strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="https://mirror.dkm.cz/gentoo"
LANG="cs_CZ.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu -Wl,--sort-common -Wl,--enable-new-dtags"
LEX="flex"
MAKEOPTS="-j8"
PKGDIR="/mnt/Distfiles/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/mnt/video/tmp"
SHELL="/bin/bash"
USE="X a52 aac acpi activities alsa amd64 avif bluetooth branding bzip2 cairo cdda cdr cet crypt cups dbus declarative dga dri dts dvd dvdr elogind encode exif flac gdbm gif gstreamer gtk gui heif iconv icu ipv6 jpeg kde kf6compat kwallet lcms libnotify libtirpc lm-sensors lvm mad mng mp3 mp4 mpeg multilib ncurses networkmanager nls ogg opencl opengl openmp openssl opus pam pango pcre pdf pipewire plasma png policykit ppds pulseaudio qml qt5 qt6 readline sdl seccomp semantic-desktop sound spell split-usr ssl startup-notification svg test-rust theora tiff truetype udev udisks unicode upower usb vaapi vorbis vulkan wayland webp widgets wifi wxwidgets x264 xattr xcb xft xinetd xml xv xvid zlib" ABI_X86="64" ADA_TARGET="gcc_14" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_anon authn_dbm authn_file authz_dbm authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir env expires ext_filter file_cache filter headers include info log_config logio mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon sheets words" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt rdrand sha sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax navcom oceanserver oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 tsip tripmate tnt ublox" GRUB_PLATFORMS="efi-64 pc" GUILE_SINGLE_TARGET="3-0" GUILE_TARGETS="3-0" INPUT_DEVICES="evdev synaptics libinput" KERNEL="linux" L10N="cs" LCD_DEVICES="bayrad cfontz glk hd44780 lb216 lcdm001 mtxorb text" LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php8-2" POSTGRES_TARGETS="postgres17" PYTHON_SINGLE_TARGET="python3_12" PYTHON_TARGETS="python3_12" RUBY_TARGETS="ruby32" SANE_BACKENDS="genesys net" VIDEO_CARDS="vesa amdgpu radeonsi" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipp2p iface geoip fuzzy condition tarpit sysrq proto logmark ipmark dhcpmac delude chaos account"
Unset: ADDR2LINE, AR, ARFLAGS, AS, ASFLAGS, CC, CCLD, CONFIG_SHELL, CPP, CPPFLAGS, CTARGET, CXX, CXXFILT, ELFEDIT, EXTRA_ECONF, F77FLAGS, FC, GCOV, GPROF, INSTALL_MASK, LC_ALL, LD, LFLAGS, LIBTOOL, LINGUAS, MAKE, MAKEFLAGS, NM, OBJCOPY, OBJDUMP, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PYTHONPATH, RANLIB, READELF, RUSTFLAGS, SIZE, STRINGS, STRIP, YACC, YFLAGS
=================================================================
Package Settings
=================================================================
www-client/chromium-135.0.7049.84::gentoo was built with the following:
USE="X cups official proprietary-codecs pulseaudio qt6 system-harfbuzz system-png system-zstd vaapi wayland -bindist -bundled-toolchain -custom-cflags -debug -ffmpeg-chromium -gtk4 -hangouts (-headless) -kerberos -pax-kernel (-pgo) -screencast (-selinux) (-system-icu) -test -widevine" ABI_X86="(64)" L10N="cs -af -am -ar -bg -bn -ca -da -de -el -en-GB -es -es-419 -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -it -ja -kn -ko -lt -lv -ml -mr -ms -nb -nl -pl -pt-BR -pt-PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -ur -vi -zh-CN -zh-TW" LLVM_SLOT="19 (-20)"
CFLAGS="-O2 -pipe -march=znver2 -mtune=znver2 -Wno-unknown-warning-option"
CXXFLAGS="-O2 -pipe -march=znver2 -mtune=znver2 -Wno-unknown-warning-option"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu -Wl,--sort-common -Wl,--enable-new-dtags -Wl,--undefined-version"
|
However, considering the progress of the chromium build indicating it has over 50 thousand build commands, I am skeptical of it being just 220 megabytes... that figure seems rather low. Maybe the arm64 version of it gets built in a different way. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 55158
Location: 56N 3W
|
| Posted: Thu Apr 17, 2025 7:38 pm Post subject: |
|
|
motig,
Heres some old build logs I have lying around built for -march=btver1. That's an old AMD E350.
| Code: | 218236 -rw-rw---- 1 portage portage 223465563 Feb 27 23:36 /usr/tuppenny/var/log/portage/www-client:chromium-133.0.6943.126:20250227-191416.log
218232 -rw-rw---- 1 portage portage 223464959 Feb 9 02:46 /usr/tuppenny/var/log/portage/www-client:chromium-133.0.6943.53:20250208-223350.log
218228 -rw-rw---- 1 portage portage 223460245 Mar 14 07:41 /usr/tuppenny/var/log/portage/www-client:chromium-133.0.6943.126:20250314-051103.log
195840 -rw-rw---- 1 portage portage 200535187 Mar 9 2024 /usr/tuppenny/var/log/portage/www-client:chromium-122.0.6261.94:20240309-151308.log
187384 -rw-rw---- 1 portage portage 191874688 Jan 2 2024 /usr/tuppenny/var/log/portage/www-client:chromium-120.0.6099.129:20240102-160704.log
162068 -rw-rw---- 1 portage portage 165950256 Nov 11 2022 /usr/tuppenny/var/log/portage/www-client:chromium-107.0.5304.87:20221111-194140.log
160704 -rw-rw---- 1 portage portage 164553641 Oct 23 2022 /usr/tuppenny/var/log/portage/www-client:chromium-106.0.5249.119:20221023-125111.log
147012 -rw-rw---- 1 portage portage 150536113 Oct 3 2023 /usr/tuppenny/var/log/portage/www-client:chromium-117.0.5938.132:20231003-112113.log
141828 -rw-rw---- 1 portage portage 145224485 Sep 11 2023 /usr/tuppenny/var/log/portage/www-client:chromium-116.0.5845.140:20230911-151414.log
141416 -rw-rw---- 1 portage portage 144802838 May 9 2023 /usr/tuppenny/var/log/portage/www-client:chromium-112.0.5615.165:20230509-154441.log
136984 -rw-rw---- 1 portage portage 140265960 Jun 27 2023 /usr/tuppenny/var/log/portage/www-client:chromium-114.0.5735.133:20230627-120924.log
136328 -rw-rw---- 1 portage portage 139594894 Jun 9 2023 /usr/tuppenny/var/log/portage/www-client:chromium-113.0.5672.126:20230608-232246.log
131176 -rw-rw---- 1 portage portage 134319296 Mar 6 2023 /usr/tuppenny/var/log/portage/www-client:chromium-109.0.5414.74-r1:20230305-234548.log
125960 -rw-rw---- 1 portage portage 128976126 Jan 16 2022 /usr/tuppenny/var/log/portage/www-client:chromium-98.0.4758.54:20220115-221042.log
124480 -rw-rw---- 1 portage portage 127459375 Nov 5 2021 /usr/tuppenny/var/log/portage/www-client:chromium-96.0.4664.27:20211105-005652.log
121192 -rw-rw---- 1 portage portage 124092718 Jun 16 2022 /usr/tuppenny/var/log/portage/www-client:chromium-102.0.5005.115:20220616-184417.log
121192 -rw-rw---- 1 portage portage 124092489 May 21 2022 /usr/tuppenny/var/log/portage/www-client:chromium-102.0.5005.61:20220521-203146.log
120316 -rw-rw---- 1 portage portage 123197319 Apr 12 2022 /usr/tuppenny/var/log/portage/www-client:chromium-101.0.4951.26:20220412-163150.log
115424 -rw-rw---- 1 portage portage 118188128 Dec 3 2021 /usr/tuppenny/var/log/portage/www-client:chromium-97.0.4692.36:20211203-194627.log
115008 -rw-rw---- 1 portage portage 117762989 Nov 5 2021 /usr/tuppenny/var/log/portage/www-client:chromium-96.0.4664.35:20211105-174533.log |
They all fall far short of 1G never mind 69G.
I don't see what you are doing to get such a huge log.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
motig
n00b
Joined: 11 Oct 2016
Posts: 44
|
| Posted: Thu Apr 17, 2025 8:14 pm Post subject: |
|
|
| Interesting. Once a new version becomes stable I will connect an external drive and store the log there for comparison and analysis. The current one has unfortunately been deleted when the build finished. I did not anticipate wanting to keep the build directory around. |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 2271
|
| Posted: Thu Apr 17, 2025 8:22 pm Post subject: |
|
|
| Might be bug 947930 if distcc is in use. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 55158
Location: 56N 3W
|
| Posted: Fri Apr 18, 2025 9:26 am Post subject: |
|
|
That will be FEATURES=icecream then.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
motig
n00b
Joined: 11 Oct 2016
Posts: 44
|
| Posted: Fri Apr 18, 2025 4:07 pm Post subject: |
|
|
| sam_ wrote: | | Might be bug 947930 if distcc is in use. |
That definitely looks like my problem. Thank you for pointing this out - I checked the forums for a similar problem but it did not occur to me that I should also check bug reports. I will mark this solved (although it's sort of a workaround).
For people who stumble upon this in the future and don't want to read the bug report: add "-Wno-gnu-line-marker" to your CFLAGS and CXXFLAGS for chromium if you are using distcc (or icecream). |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
