[SOLVED] Chromium fails to compile in Gentoo

fakie_flip · 07-11-2012, 12:50 AM

Here is the last bit of output from emerge www-clients/chromium: This took forever, I mean about 2 days on 1 ghz pentium 3. I am still without a web-browser on Gentoo =\

http://vpaste.net/DwsQc

Here is the output of two commands suggested I use by the last output:

http://vpaste.net/2a6im

Slackyman · 07-11-2012, 01:27 AM

And what about the content of /var/tmp/portage/www-client/chromium-20.0.1132.43/temp/build.log?

segmentation_fault · 07-11-2012, 05:50 AM

Do you have enough RAM/hard disk space to compile chromium? Is your memory tested (eg with memtest86) ?

whizzit · 07-12-2012, 07:41 AM

I have recently found that chromium requires about 6GB of RAM to compile on my 64bit system (with options gnome, cups and all the locales). Whilst my system RAM had 4GB it obviously started swapping at some point and subsequently progress was much slower, as expected.

It's a beast to compile and the persuading reason for me to buy more RAM. If your CPU is 32 bit then this will continue to be an issue for you as you'll be limited to 4GB of RAM.

segmentation_fault · 07-12-2012, 08:30 AM

6GB RAM? wow!I compile firefox on my netbook with 1GB.
Anyway, if you need a web browser quickly, you can install firefox-bin (precompiled firefox), as there is no chromium-bin on the official portage tree.

whizzit · 07-12-2012, 12:01 PM

True, I use firefox as my number 2 and epiphany as my number 3

A little bit of research shows that it's the linking that is the big RAM user and the recommended[1] build host is a 64 bit host:

Quote:

Even if you're building a 32-bit executable, you need a 64-bit machine since linking requires >4GB virtual memory.

As chance would have it I upgraded to chromium 20.0.1132.57 today. These are my simple build stats for emerge, package creation and installation:

ged # time LINGUAS="bg en_GB uk" emerge -vu chromium
...
real 58m10.508s
user 140m58.502s
sys 22m12.761s

ld was the RAM hog taking ~34% of 12GB ( not closely monitored to see the max ). Bear in mind this is also using -j4 in /etc/make.conf on a 3.x GHz quad-core Phenom II. It was much slower when on 4GB, 3-4 hrs maybe.

However, my emerge sync is from today and the build was successful. Note that it's a minor bump from the version the OP was trying to build, .43 vs .57.

So I guess the solutions for the OP could be:

Get chromium built on a 64 bit host somewhere ( cloud VM perhaps? )
Use an alternative GUI browser ( /usr/portage/www-client/ )
Use pre-built chromium built binaries, if available for gentoo hardened ( as the OP is using )
Try release 20.0.1132.57 in case .43 did have a build bug (?) whilst keeping fingers crossed.

Regards,

Grant

[1] http://www.chromium.org/Home - "Life of a Chromium Developer" - slide 10.

fakie_flip · 07-13-2012, 08:45 AM

RAM is definitely the issue. I have 512mb ram, and 512mb swap also, 1ghz cpu. Before chromium failed on compile, it was taking at least 2 days to get that far. I found out chromium may not of been as light weight as I thought, so I am using uzbl-tabbed and might also install midori. I have a desktop with 4gb ram, 64-bit Fedora, and 2.8ghz cpu. I've been trying to get distcc working. I'll make another post for that.

How can I clean up from the half install/emerge of chromium since I won't be using it?

How can I remove the dependencies that were compiled and installed for chromium through emerge?

segmentation_fault · 07-13-2012, 08:53 AM

Code:

 # emerge --depclean

will remove any packages that are not in the world file, and are not needed by any other package. Run it with --pretend first, to verify what is going to be removed.

Code:

 # eclean -d distfiles

will clean up your distfiles directory. See the man pages of those tools.

i92guboj · 07-13-2012, 12:49 PM

You definitely don't need 6gb of ram to compile this, I don't have that amount not even taking into account my swap space.

Being that said, I wouldn't compile this in such machine. Just use a binary package or choose another browser.

fakie_flip · 07-15-2012, 11:42 PM

I guess I will mark this as solved because I understand the reason why it failed. I could have distcc compile it for me. It's working just fine and great now btw. http://i.imgur.com/zD6i1.jpg and http://img6.imagebanana.com/img/fgzr...llRunningO.png

BTW, I am using Uzbl Tabbed uzbl-tabbed right now, and I love it, light weight for my computer with limited resources and I can browse the web entire with the keyboard like VIM, never really need to touch the mouse. I might add Midori just to have a backup browser I can use or something else to experiment with, not sure tho. Firefox would definitely clobber all my RAM, then swap and then say FEED ME MORE!

Da_Nuke · 06-10-2013, 03:05 PM

Bumping this thread because the same error just happened to me on VMware Player with 1 GB of allocated RAM. I solved this by increasing the VM's RAM to 2 GB.

Also, I recently compiled Chromium successfully on my Pentium Dual Core with 2 GB of DDR1.

Also, as a little bonus, if you have a small Linux partition and emerge complains about low disk space (such as in LibreOffice requiring like 6 GB of temporary space), try setting up a loop device and linking /var/tmp to your loop device, like this:

Code:

# dd if=/dev/zero of=/media/2TBDRIVE/temporaryfilesystemforportage.dd bs=1G count=30
# losetup /dev/loop0 /media/2TBDRIVE/temporaryfilesystemforportage.dd
# mkfs.<yr favorite filesystem> /dev/loop0
# mount /dev/loop0 /media/PORTAGETEMP
# cd /var/tmp
# cp -r * /media/PORTAGETEMP
# cd /var
# rm -rf tmp
# ln -s /media/PORTAGETEMP tmp