Re: [gentoo-user] OpenOffice build failed

[Meino Christian Cramer <Meino.Cramer@gmx.de>]

Hi,

 first of all: A BIG thank you to all that send replies to my initial
 cry. :)

 The real reason behind the unsuccessful build of OpenOffice was a
 wrong PYTHONPATH, which I had fixed in the user settings but not for
 the root account. They were rests from older settings, which I had
 took over when starting with Gentoo.

 The current build took five hours to finish, the CPU does not exceeds
 a core temperature of 45.5 degree celsius and the 9.1 GByte on /tmp
 were enough. Now I will remove the temporary installed symlink from
 /var/tmp/portage.

 Openoffice runs well in a quick test.

 Thank you again for all your help!
 Kind regards,
 Meino



 PS: May be it would be an idea to run a "system sanity check script"
 before such megabuilds, which quickly not only checks for missing
 software dependencies (which is already done) but also for a clean
 environment AND STOP the build, if anything is wrong.

 For example: An automatic echo on the console like "found only
 5GBytes (need 9GBytes) on /var/tmp/portage ...you have 3 seconds to
 abort with ^C or I will continue" will not help for psychological
 reasons: One who starts such a megabuild (and knows it will run for
 hours) will press <RETURN> after the specific command and will go to
 bed.

 My suggestion would be to abort hard at once and only when given with
 option "-f space" (force) will ignore _only_ the warning about
 missing free space on hd. Other warnings will still be able to abort.

 This way, the PYTHONPATH problem would have been discovered right in
 the start phase and not after the whole build process when it comes
 to the install process.

 Only my two cents -- your mileage may vary.
 Keep hacking!
 Meino

-- 
gentoo-user@gentoo.org mailing list