Talk:Chromium

Note
This is a Talk page - please see the documentation about using talk pages. Add newer comments below older ones, sign comments using four tildes (~~~~), and indent successive comments with colons (:). Add new sections at the bottom of the page, under a heading (== ==). Please remember to mark sections as "open for discussion" using {{talk|open}}, so they will show up in the list of open discussions.

Wayland

Talk status

This discussion is done.

Why Chromium still not support wayland? — The preceding unsigned comment was added by AMID EVIL (talk • contribs) May 18, 2016‎

Not sure. Ask upstream? --Maffblaster (talk) 17:11, 1 November 2016 (UTC)

Emerge not respecting -j switch

Talk status

This discussion is done.

Chrome will start 6 threads even if make.conf has -j=1 This is very annoying when even though -j=1, suddenly one is caught out when Emerge fires off 6 threads on all cpus, overheating the laptop and nearly starting a catastrophic melt down!

To force Emerge to run all 6 threads on one cpu, set the cpu affinity with command taskset. Thus for one cpu:

root #taskset -c 0 emerge www-client/chromium

For multiple cpus, in this case 3 cpus as in cpu 0,1,2:

root #taskset -c 0-2 emerge www-client/chromium

How long does it take to compile Chromium? Use genlop to find this out. This is for an i5 at 3.3Ghz on one cpu:

root #genlop -t chromium

Mon Mar 20 08:10:16 2017 >>> www-client/chromium-57.0.2987.98
merge time: 10 hours, 31 minutes and 23 seconds.

I respectfully request this be added to the main wiki page toward helping Gentoo users keep their machines in good order while Chromium is emerged.

--Russelld (talk) 08:20, 20 March 2017 (UTC)

Hi Russelld , if this is true is sounds to me like there's a bug in the Chromium ebuild. Instead of adding a section here on the wiki about it, since this is not how Portage is supposed to operate, you should file a bug on our Bugzilla against the Chromium ebuild(s). This was the issue will be brought to the attention of the package developer and they can make the necessary changes to correct this behavior. Also, if you still think it necessary to add something concerning this (incorrect) behavior to the Chromiumarticle, you'll need to do it yourself (probably best if you add it in a Troubleshooting section with a temporary work around). This is publicly editable wiki. Kind regards, --Maffblaster (talk) 16:48, 20 March 2017 (UTC)

Replace linguas by L10N

Talk status

This discussion is done as of 2022-01-19.

Chromium uses L10N instead of linguas. I have suggested a modification in this revision (with misspelled L10n, ups!), but I am unsure of the modification as the Localization/Guide mentions both variables. Mimosinnet (talk) 19:13, 8 December 2020 (UTC)

You are correct, L10N is presently what is in use by the chromium eclass. I have made this edit to help clarify: Special:Diff/1011771/1043607. --Maffblaster (talk) 00:22, 20 January 2022 (UTC)