Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 390041 - app-office/libreoffice should be able to use less than 1GB RAM to build
Summary: app-office/libreoffice should be able to use less than 1GB RAM to build
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: ARM Linux
: Normal normal
Assignee: Gentoo Office Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-10 00:20 UTC by Bernhard Nägele
Modified: 2011-11-10 18:44 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Nägele 2011-11-10 00:20:32 UTC
I want to build libreoffice-9999-r1 on an ARM architecture based platform (Toshiba AC100) with 512MB RAM.

During pre-merge checks for app-office/libreoffice-9999-r1 I got the message 

* There is NOT at lease 1 gibibytes RAM

* Space constrains set in the ebuild were not met!

and emerge stops.

I think there must be a way to build this package even if it has less RAM. The compiled binary may be slow, but there should be the possibility to build the package.
Comment 1 Vincent de Phily 2011-11-10 10:29:39 UTC
I believe the reason it needs so much ram is because some of the LO source files are huge and GCC needs that much ram to compile them. Linking the final binaries together might also take a lot of ram.

You can always try "I_KNOW_WHAT_I_AM_DOING=yes emerge libreoffice" to ignore the check and see what happens.

You'll at least want to check that your system is compiled with CFLAGS=-Os and libreoffice is compiled with MAKEOPTS=-j1. Have the bare minimum programs running (no GUI desktop). Not sure what else can help, short of swapping ld with gold and/or gcc with clang. If you've got enough swap space, compilation will probably not so mauch fail as take forever to complete.
Comment 2 Tomáš Chvátal (RETIRED) gentoo-dev 2011-11-10 18:44:48 UTC
1) It has no arm keywords.
2) The 1 GB is checked on amd64 one thread build.

So the constrains are set to be some sane minimal, if you trust you can build it on your machine you can always disable the check with the I_KNOW_WHAT_I_AM_DOING variable.

This is something that we won't fix. For sake of few I won't break build for many.