| View previous topic :: View next topic |
| Author |
Message |
jagdpanther
l33t
Joined: 22 Nov 2003
Posts: 729
|
 Posted: Fri Oct 12, 2018 7:14 pm Post subject: |
 |
|
| Quote: | | - try ver. 70 ( it will fail probably too) |
Yes you are correct. 70.0.3538.45 also failed.
| Quote: | | find why its badly unpacked ( maybe some system packages are not updated ?) |
I don't think anything is out-of-date. I run
"emerge --update --deep --newuse --with-bdeps=y @world " almost daily.
However, I have had cases over the years when re-emerging a not-out-of-date package fixed an issue.
( I was thinking of trying re-emerging all dependencies but that involved 423 packages
emerge --emptytree chromium -p | wc -l
423 )
| Quote: | | After doubling my RAM to 16Gb Chromium 69.0.3497.100 compiled successfully. |
I have 64GB on this system so not-enough-memory should not be my issue.
| Quote: | | unpack manually and when chromium starts compilng copy files to work dir |
Interesting idea, I may try this. |
|
| Back to top |
|
 |
jagdpanther
l33t
Joined: 22 Nov 2003
Posts: 729
|
| Posted: Mon Oct 15, 2018 5:13 pm Post subject: |
|
|
After reading the Gentoo Chromium web page, https://wiki.gentoo.org/wiki/Chromium I added the icu use flag to the portage make.conf file and removed the individual "icu" use flags I set for dev-libs/libxml2 and net-libs/nodejs. I then ran 'emerge --update --deep --newuse --exclude chromium @world " and three packages were re-emerged with the icu use flag: sqlite, boost and re2.
I then tried to emerge chromium again (chromium-69.0.3497.100) and did NOT receive the the missing file, brotli/enc/static_dict.c error. Instead, I get:
| Code: | fatal error: error in backend: Unable to copy EFLAGS physical register!
x86_64-pc-linux-gnu-clang++: error: clang frontend command failed with exit code 70 (use -v to see invocation)
clang version 6.0.1 (tags/RELEASE_601/final) |
Which is at the end of:
| Code: | x86_64-pc-linux-gnu-clang++ -MMD -MF obj/chrome/browser/ui/ui/tab.o.d -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DUSE_CUPS -DUSE_GIO -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -DENABLE_IPC_FUZZER -DTOOLKIT_VIEWS=1 -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DVK_NO_PROTOTYPES -DEXPAT_RELATIVE_PATH -DGOOGLE_PROTOBUF_NO_RTTI -DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -DLEVELDB_PLATFORM_CHROMIUM=1 -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 -DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE -DUCHAR_TYPE=uint16_t -DV8_USE_EXTERNAL_STARTUP_DATA -DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS -DSK_HAS_PNG_LIBRARY -DSK_HAS_WEBP_LIBRARY -DSK_HAS_JPEG_LIBRARY -DSK_VULKAN_HEADER=\"../../skia/config/SkVulkanConfig.h\" -DSK_VULKAN=1 -DSK_SUPPORT_GPU=1 -DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\" -DVK_NO_PROTOTYPES -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DGTEST_RELATIVE_PATH -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX -DABSL_ALLOCATOR_NOTHROW=1 -DNO_MAIN_THREAD_WRAPPING -DI18N_ADDRESS_VALIDATION_DATA_URL=\"https://chromium-i18n.appspot.com/ssl-aggregate-address/\" -DUSE_SYSTEM_ZLIB=1 -I../.. -Igen -Igen/shim_headers/zlib_shim -Igen/shim_headers/re2_shim -Igen/shim_headers/snappy_shim -Igen/shim_headers/libpng_shim -Igen/shim_headers/libwebp_shim -Igen/shim_headers/libdrm_shim -I../../third_party/khronos -I../../gpu -I../../third_party/libyuv/include -I../../third_party/vulkan/include -Igen/shim_headers/openh264_shim -Igen/shim_headers/minizip_shim -Igen/shim_headers/flac_shim -I../../third_party/webrtc_overrides -I../../testing/gtest/include -I../../third_party/libyuv/include -I../../third_party/usrsctp/usrsctplib -I../../third_party/webrtc -I../../third_party/protobuf/src -Igen/protoc_out -I../../third_party/protobuf/src -I../../third_party/boringssl/src/include -I../../third_party/leveldatabase -I../../third_party/leveldatabase/src -I../../third_party/leveldatabase/src/include -I../../third_party/ced/src -I../../third_party/icu/source/common -I../../third_party/icu/source/i18n -I../../skia/config -I../../skia/ext -I../../third_party/skia/include/c -I../../third_party/skia/include/config -I../../third_party/skia/include/core -I../../third_party/skia/include/effects -I../../third_party/skia/include/encode -I../../third_party/skia/include/gpu -I../../third_party/skia/include/images -I../../third_party/skia/include/lazy -I../../third_party/skia/include/pathops -I../../third_party/skia/include/pdf -I../../third_party/skia/include/pipe -I../../third_party/skia/include/ports -I../../third_party/skia/include/utils -I../../third_party/vulkan/include -I../../third_party/skia/third_party/vulkanmemoryallocator -I../../third_party/skia/src/gpu -I../../third_party/skia/src/sksl -I../../third_party/vulkan/include -I../../third_party/libwebm/source -I../../v8/include -Igen/v8/include -I../../third_party/webrtc_overrides -I../../third_party/webrtc -I../../third_party/perfetto/include -Igen/third_party/perfetto/protos -Igen/third_party/perfetto/protos -Igen/third_party/perfetto/protos -Igen/third_party/metrics_proto -I../../third_party/mesa/src/include -Igen -Igen -I../../third_party/libaddressinput/src/cpp/include -I../../third_party/cacheinvalidation/overrides -I../../third_party/cacheinvalidation/src -I../../third_party/flatbuffers/src/include -I../../third_party/brotli/include -I../../third_party/webrtc_overrides -I../../testing/gtest/include -I../../third_party/webrtc -Igen -Igen -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= -funwind-tables -fPIC -pthread -fcolor-diagnostics -fmerge-all-constants -no-canonical-prefixes -Wall -Wextra -Wimplicit-fallthrough -Wthread-safety -Wno-missing-field-initializers -Wno-unused-parameter -Wno-c++11-narrowing -Wno-covered-switch-default -Wno-unneeded-internal-declaration -Wno-undefined-var-template -Wno-address-of-packed-member -Wno-nonportable-include-path -Wno-user-defined-warnings -Wno-unused-lambda-capture -Wno-null-pointer-arithmetic -Wno-enum-compare-switch -fno-omit-frame-pointer -fvisibility=hidden -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wno-nonnull -Wexit-time-destructors -isystem../../../../../../../../../usr/include/glib-2.0 -isystem../../../../../../../../../usr/lib64/glib-2.0/include -isystem../../../../../../../../../usr/include/glib-2.0 -isystem../../../../../../../../../usr/lib64/glib-2.0/include -Wno-header-guard -isystem../../../../../../../../../usr/include/nss -isystem../../../../../../../../../usr/include/nspr -isystem ../../third_party/abseil-cpp -Wno-exit-time-destructors -isystem../../../../../../../../../usr/include/dbus-1.0 -isystem../../../../../../../../../usr/lib64/dbus-1.0/include -std=gnu++14 -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -march=native -O2 -pipe -c ../../chrome/browser/ui/views/tabs/tab.cc -o obj/chrome/browser/ui/ui/tab.o
fatal error: error in backend: Unable to copy EFLAGS physical register!
x86_64-pc-linux-gnu-clang++: error: clang frontend command failed with exit code 70 (use -v to see invocation)
clang version 6.0.1 (tags/RELEASE_601/final)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/lib/llvm/6/bin |
I guess it is a good thing that chromium-68.0.3440.75 , the last successful chromium emerge I did, still works. |
|
| Back to top |
|
|
jagdpanther
l33t
Joined: 22 Nov 2003
Posts: 729
|
| Posted: Fri Nov 23, 2018 8:00 pm Post subject: |
|
|
Without making any additional changes I tried emerging chromium-70.0.3538.110 and it completed without issue.
Chromium-70.0.3538.110 works. (ie. I can watch Netflix, just about the only use I make of chromium.)
I still don't know why I couldn't upgrade (via portage) chromium for a while. (At least I learned that the
jumbo-build use flag significantly reduces Chromium's build time.)
I added "solved" to the subject, but that is a misnomer.
Last edited by jagdpanther on Sat Nov 24, 2018 5:33 pm; edited 1 time in total |
|
| Back to top |
|
|
Oniryczny
Guru
Joined: 01 Dec 2011
Posts: 419
Location: Poland
|
| Posted: Sat Nov 24, 2018 11:06 am Post subject: |
|
|
I am trying today update to 70.0.3583.110 but I get ninja errors  | Code: |
[7860/9961] x86_64-pc-linux-gnu-g++ -MMD -MF obj/headless/headless/headless_browser_impl.o.d -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DHEADLESS_IMPLEMENTATION -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DVK_NO_PROTOTYPES -DGOOGLE_PROTOBUF_NO_RTTI -DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD -DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS -DSK_HAS_PNG_LIBRARY -DSK_HAS_WEBP_LIBRARY -DSK_HAS_JPEG_LIBRARY -DSK_VULKAN_HEADER=\"../../skia/config/SkVulkanConfig.h\" -DSK_VULKAN=1 -DSK_SUPPORT_GPU=1 -DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\" -DVK_NO_PROTOTYPES -DV8_DEPRECATION_WARNINGS -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 -DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE -DUCHAR_TYPE=uint16_t -DV8_USE_EXTERNAL_STARTUP_DATA -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX -DABSL_ALLOCATOR_NOTHROW=1 -DNO_MAIN_THREAD_WRAPPING -DLEVELDB_PLATFORM_CHROMIUM=1 -DV8_DEPRECATION_WARNINGS -I../.. -Igen -Igen/shim_headers/zlib_shim -Igen/shim_headers/libpng_shim -Igen/shim_headers/libwebp_shim -I../../third_party/libyuv/include -Igen/shim_headers/openh264_shim -Igen/shim_headers/re2_shim -Igen/shim_headers/libdrm_shim -Igen/shim_headers/snappy_shim -I../../third_party/khronos -I../../gpu -I../../third_party/vulkan/include -I../../third_party/protobuf/src -Igen/protoc_out -I../../third_party/protobuf/src -I../../third_party/boringssl/src/include -I../../skia/config -I../../skia/ext -I../../third_party/skia/include/c -I../../third_party/skia/include/config -I../../third_party/skia/include/core -I../../third_party/skia/include/effects -I../../third_party/skia/include/encode -I../../third_party/skia/include/gpu -I../../third_party/skia/include/images -I../../third_party/skia/include/lazy -I../../third_party/skia/include/pathops -I../../third_party/skia/include/pdf -I../../third_party/skia/include/pipe -I../../third_party/skia/include/ports -I../../third_party/skia/include/utils -I../../third_party/vulkan/include -I../../third_party/skia/third_party/vulkanmemoryallocator -I../../third_party/skia/src/gpu -I../../third_party/skia/src/sksl -I../../third_party/skia/modules/skottie/include -I../../third_party/vulkan/include -I../../v8/include -Igen/v8/include -I../../third_party/icu/source/common -I../../third_party/icu/source/i18n -I../../third_party/ced/src -I../../third_party/webrtc_overrides -I../../third_party/webrtc -I../../third_party/abseil-cpp -I../../third_party/leveldatabase -I../../third_party/leveldatabase/src -I../../third_party/leveldatabase/src/include -I../../third_party/libwebm/source -I../../v8/include -Igen/v8/include -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= -funwind-tables -fPIC -pipe -pthread -Wall -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-missing-field-initializers -Wno-unused-parameter -fno-omit-frame-pointer -fvisibility=hidden -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/nss -I/usr/include/nspr -std=gnu++14 -Wno-narrowing -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -O2 -march=bdver2 -pipe -c ../../headless/lib/browser/headless_browser_impl.cc -o obj/headless/headless/headless_browser_impl.o
ninja: build stopped: subcommand failed.
* ERROR: www-client/chromium-70.0.3538.110::gentoo failed (compile phase):
* ninja -v -j7 -l0 -C out/Release chrome chromedriver failed
*
* Call stack:
* ebuild.sh, line 124: Called src_compile
* environment, line 5001: Called eninja '-C' 'out/Release' 'chrome' 'chromedriver'
* environment, line 1771: Called die
* The specific snippet of code:
* "$@" || die "${nonfatal_args[@]}" "${*} failed"
|
_________________
cogito ergo sum |
|
| Back to top |
|
|
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 30888
Location: here
|
| Posted: Sat Nov 24, 2018 11:13 am Post subject: |
|
|
You can post full build.log?
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
Olis
Apprentice
Joined: 29 Sep 2004
Posts: 177
Location: Germany
|
| Posted: Sat Nov 24, 2018 1:03 pm Post subject: |
|
|
I also had massive problems emerging chromium-70.0.3538.110. For me it was purely a resource problem.
I checked my system half an hour after starting emerge of chromium-70.0.3538.110 and found it frozen. I was able to ssh from another pc but system was too slow to kill any processes, so I switched it off. Next time I emerged chromium I was working at the system when it froze again. On the third run I had "top" running in a seperate console session and found that emerge consumed all my memory (14 GB RAM + 8 GB swap).
Next try was without ccache, but it didn't help. It just took much longer for the system to run out of memory (1,5 hours vs. 3-4 minutes).
I enabled ccache again and reduced MAKEOPTS in /etc/portage/make.conf fom "-j7" to "-j4" (old Sandybridge Core i7). I aborted emerge when free swap space felt below 500 MB.
So I reduced MAKEOPTS to "-j2" and this time chromium-70.0.3538.110 compiled without problems (merge time: 42 minutes and 48 seconds.) I didn't watch "top" all the time but the peak memory consumption I saw was one compiler process (cc1plus) consuming 5.7 GB and the second one 3.x GB RAM. So the emerge check for "at least 3 GiB RAM" seems to be outdated.
I don't know what changed from my previous version (70.0.3538.67) which compiled without problems using ccache and "-j7". This pc is 5 years old and I'm not planning to replace any memory modules anymore. |
|
| Back to top |
|
|
Oniryczny
Guru
Joined: 01 Dec 2011
Posts: 419
Location: Poland
|
| Posted: Sat Nov 24, 2018 8:04 pm Post subject: |
|
|
| Code: | $ wgetpaste /var/tmp/portage/www-client/chromium-70.0.3538.110/temp/build.log
The input source: "/var/tmp/portage/www-client/chromium-70.0.3538.110/temp/build.log" is not readable. Please specify a readable input source. |
WTF I have never had such problems... How can I show you the build log then?
_________________
cogito ergo sum |
|
| Back to top |
|
|
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 30888
Location: here
|
| Posted: Sat Nov 24, 2018 9:13 pm Post subject: |
|
|
I'm not sure but probably because is too large the file. You can open file with less? If yes put file in dropbox or similar
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
ct85711
Veteran
Joined: 27 Sep 2005
Posts: 1791
|
| Posted: Sat Nov 24, 2018 9:32 pm Post subject: |
|
|
| The error message more of indicates more of a permissions issue, specially as it looks like you tried reading the file (owned by portage:portage) as a regular user. On my system, build.log owner is portage:portage with 550 on permissions. So more likely he needs to use su/sudo so he has permission to access the file. |
|
| Back to top |
|
|
Olis
Apprentice
Joined: 29 Sep 2004
Posts: 177
Location: Germany
|
| Posted: Sun Nov 25, 2018 9:34 am Post subject: |
|
|
| Olis wrote: | | I don't know what changed from my previous version (70.0.3538.67) which compiled without problems using ccache and "-j7". This PC is 5 years old and I'm not planning to replace any memory modules anymore. |
Possible reason: I enabled the USE flag "jumbo-build". This reduces compilation time, but requires a lot of memory. I disabled the flag again. |
|
| Back to top |
|
|
Muso
Veteran
Joined: 22 Oct 2002
Posts: 1052
Location: The Holy city of Honolulu
|
| Posted: Sun Nov 25, 2018 10:02 am Post subject: |
|
|
| Olis wrote: | | Olis wrote: | | I don't know what changed from my previous version (70.0.3538.67) which compiled without problems using ccache and "-j7". This PC is 5 years old and I'm not planning to replace any memory modules anymore. |
Possible reason: I enabled the USE flag "jumbo-build". This reduces compilation time, but requires a lot of memory. I disabled the flag again. |
When building Chromium without "jumbo-build", it took me 4 1/2 hours on an 8 core, 3.5 ghz/core processor running -j9 with 16gb of ram. Trying out "jumbo-build", it locked the system... so I ordered a new set of ram (instead of 4x4gb, 4x8gb). With 32gb of ram it didn't lock up and built in under 90 minutes.
_________________
"You can lead a horticulture but you can't make her think" ~ Dorothy Parker
2021 is the year of the Linux Desktop! |
|
| Back to top |
|
|
Oniryczny
Guru
Joined: 01 Dec 2011
Posts: 419
Location: Poland
|
|
| Back to top |
|
|
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 30888
Location: here
|
| Posted: Sun Nov 25, 2018 11:32 am Post subject: |
|
|
| Code: | | x86_64-pc-linux-gnu-g++: internal compiler error: Killed (program cc1plus) |
I clearly an out of memory error
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
Oniryczny
Guru
Joined: 01 Dec 2011
Posts: 419
Location: Poland
|
| Posted: Sun Nov 25, 2018 12:56 pm Post subject: |
|
|
I have never had out of memory issues I have 16GB RAM installed
is there any way to solve it without adding more RAM ?
_________________
cogito ergo sum |
|
| Back to top |
|
|
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 30888
Location: here
|
| Posted: Sun Nov 25, 2018 1:08 pm Post subject: |
|
|
| Oniryczny wrote: | I have never had out of memory issues I have 16GB RAM installed
is there any way to solve it without adding more RAM ? |
Decrease makeopts value can help or disable jumbo-build use flag (this increase a lot the build time)
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
Oniryczny
Guru
Joined: 01 Dec 2011
Posts: 419
Location: Poland
|
| Posted: Sun Nov 25, 2018 6:37 pm Post subject: |
|
|
I thought jumbo-build was to help but I see its bad now
I didn't USE it and chromium compilled succesfully... after TIME | Code: |
# genlop -t chromium
* www-client/chromium
...
Sun Nov 25 19:28:51 2018 >>> www-client/chromium-70.0.3538.110
merge time: 5 hours, 10 minutes and 21 seconds.
# |
_________________
cogito ergo sum |
|
| Back to top |
|
|
Olis
Apprentice
Joined: 29 Sep 2004
Posts: 177
Location: Germany
|
| Posted: Sun Nov 25, 2018 8:50 pm Post subject: |
|
|
| Oniryczny wrote: | I thought jumbo-build was to help but I see its bad now
I didn't USE it and chromium compilled succesfully... after TIME | Code: |
# genlop -t chromium
* www-client/chromium
...
Sun Nov 25 19:28:51 2018 >>> www-client/chromium-70.0.3538.110
merge time: 5 hours, 10 minutes and 21 seconds.
# |
|
Using ccache might help, at least for minor updates. I "recompiled" chromium today after disabling "jumbo-build" and it just took less than 6 minutes (14 GB RAM, Sandybridge Core i7, "-j7"):
| Code: | Sun Nov 25 10:05:57 2018 >>> www-client/chromium-70.0.3538.110
merge time: 5 minutes and 54 seconds. |
The update from 70.0.3538.67 yesterday with ccache, but only 2 cores (-j2):
| Code: | Sat Nov 24 12:28:53 2018 >>> www-client/chromium-70.0.3538.110
merge time: 42 minutes and 48 seconds. |
|
|
| Back to top |
|
|
Muso
Veteran
Joined: 22 Oct 2002
Posts: 1052
Location: The Holy city of Honolulu
|
| Posted: Sun Nov 25, 2018 9:35 pm Post subject: |
|
|
| Oniryczny wrote: | I thought jumbo-build was to help but I see its bad now
I didn't USE it and chromium compilled succesfully... after TIME | Code: |
# genlop -t chromium
* www-client/chromium
...
Sun Nov 25 19:28:51 2018 >>> www-client/chromium-70.0.3538.110
merge time: 5 hours, 10 minutes and 21 seconds.
# |
|
I built the new one this morning with "jumbo-build" and watched my ram usage. My system went down to 6 gb of ram from 32. So "jumbo-build" ate something around 26 gb of ram.
| Code: | genlop -t chromium
* www-client/chromium
Thu Nov 15 23:09:29 2018 >>> www-client/chromium-71.0.3578.30
merge time: 4 hours, 31 minutes and 47 seconds.
Wed Nov 21 14:10:46 2018 >>> www-client/chromium-71.0.3578.53
merge time: 1 hour, 27 minutes and 27 seconds.
Sun Nov 25 10:42:55 2018 >>> www-client/chromium-71.0.3578.62
merge time: 1 hour, 31 minutes and 1 second.
|
_________________
"You can lead a horticulture but you can't make her think" ~ Dorothy Parker
2021 is the year of the Linux Desktop! |
|
| Back to top |
|
|
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 30888
Location: here
|
| Posted: Mon Nov 26, 2018 6:46 am Post subject: |
|
|
| Muso wrote: | | So "jumbo-build" ate something around 26 gb of ram. |
for a browser 
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
Muso
Veteran
Joined: 22 Oct 2002
Posts: 1052
Location: The Holy city of Honolulu
|
| Posted: Mon Nov 26, 2018 6:52 am Post subject: |
|
|
| fedeliallalinea wrote: | | Muso wrote: | | So "jumbo-build" ate something around 26 gb of ram. |
for a browser |
Indeed.
_________________
"You can lead a horticulture but you can't make her think" ~ Dorothy Parker
2021 is the year of the Linux Desktop! |
|
| Back to top |
|
|
Oniryczny
Guru
Joined: 01 Dec 2011
Posts: 419
Location: Poland
|
| Posted: Mon Nov 26, 2018 8:39 am Post subject: |
|
|
I have never tried ccache 
I have AMD FX-6300 ~4,2GHz 16GB RAM and I also have -j7 set in my make.conf
and never experienced such issues with updating 
_________________
cogito ergo sum |
|
| Back to top |
|
|
Olis
Apprentice
Joined: 29 Sep 2004
Posts: 177
Location: Germany
|
| Posted: Wed Nov 28, 2018 5:46 am Post subject: |
|
|
| Oniryczny wrote: | I have never tried ccache
I have AMD FX-6300 ~4,2GHz 16GB RAM and I also have -j7 set in my make.conf
and never experienced such issues with updating |
The problem wasn't ccache, but the USE flag "jumbo-build". Together with "-j7" chromium ate all my memory (16 GB RAM + 8 GB swap) during compilation. "-j2" worked.
ccache reduces compile time when emerging minor updates like from 70.0.3538.67 to 70.0.3538.110 as a lot of source files haven't changed and don't require to be compiled again. I gave ccache 5 GB of disk space on my SSD. |
|
| Back to top |
|
|
Oniryczny
Guru
Joined: 01 Dec 2011
Posts: 419
Location: Poland
|
| Posted: Wed Nov 28, 2018 8:12 pm Post subject: |
|
|
| Code: | genlop -t chromium
...
Wed Nov 28 20:57:42 2018 >>> www-client/chromium-70.0.3538.110
merge time: 16 minutes and 29 seconds.
# |
YAY it helped 
I have installed Kingston KC300 SSD drive and made /ccache folder in there
MAKEOPTS=-j3 USE="jumbo-build"
_________________
cogito ergo sum |
|
| Back to top |
|
|
Muso
Veteran
Joined: 22 Oct 2002
Posts: 1052
Location: The Holy city of Honolulu
|
| Posted: Thu Nov 29, 2018 10:14 pm Post subject: |
|
|
| Oniryczny wrote: | | Code: | genlop -t chromium
...
Wed Nov 28 20:57:42 2018 >>> www-client/chromium-70.0.3538.110
merge time: 16 minutes and 29 seconds.
# |
YAY it helped
I have installed Kingston KC300 SSD drive and made /ccache folder in there
MAKEOPTS=-j3 USE="jumbo-build" |
Nice. This prompted me to grab another SSD and move /home to it, so I could then have plenty of space on / for ccache.
| Code: | genlop -t chromium
* www-client/chromium
Thu Nov 15 23:09:29 2018 >>> www-client/chromium-71.0.3578.30
merge time: 4 hours, 31 minutes and 47 seconds.
Wed Nov 21 14:10:46 2018 >>> www-client/chromium-71.0.3578.53
merge time: 1 hour, 27 minutes and 27 seconds.
Sun Nov 25 10:42:55 2018 >>> www-client/chromium-71.0.3578.62
merge time: 1 hour, 31 minutes and 1 second.
Thu Nov 29 11:51:18 2018 >>> www-client/chromium-71.0.3578.62
merge time: 1 hour, 38 minutes and 36 seconds.
Thu Nov 29 12:02:36 2018 >>> www-client/chromium-71.0.3578.62
merge time: 7 minutes and 28 seconds.
|
Now this is nice. I'll do an emerge -e @world when I go to sleep tonight so that the ccache is built up for everything.
_________________
"You can lead a horticulture but you can't make her think" ~ Dorothy Parker
2021 is the year of the Linux Desktop! |
|
| Back to top |
|
|
Oniryczny
Guru
Joined: 01 Dec 2011
Posts: 419
Location: Poland
|
| Posted: Fri Nov 30, 2018 1:30 pm Post subject: |
|
|
I borrowed RAM from work and installed 32GB 1600MHz
now I could try standard with -j7 from my make.conf and I got: | Code: |
# genloop -t chromium
...
Fri Nov 30 13:05:34 2018 >>> www-client/chromium-70.0.3538.110
merge time: 8 minutes and 35 seconds.
Sat Dec 1 22:53:18 2018 >>> www-client/chromium-71.0.3578.53
merge time: 1 hour, 37 minutes.
Sun Dec 2 11:06:56 2018 >>> www-client/chromium-71.0.3578.62
merge time: 47 minutes and 42 seconds.
|
EDIT
Maybe ~ isn't using ccache?
_________________
cogito ergo sum
Last edited by Oniryczny on Sun Dec 02, 2018 10:16 am; edited 3 times in total |
|
| Back to top |
|
|
|
Portage & Programming
