Re: [gentoo-user] Openoffice 2 Install problems
WORD OF WARNING. I HAVE NEVER DONE THIS! I think it is in make.conf. Looks something like this: # PORTAGE_TMPDIR is the location portage will use for compilations and # temporary storage of data. This can get VERY large depending upon # the application being installed. #PORTAGE_TMPDIR=/var/tmp I would assume you would change that to say PORTAGE_TMPDIR=/mnt/data or whereever you have the most space. Don't forget to remove the # though. May want to change it back afterwords too. It got really big on mine. It was likely about 4 or 5GBs before it was done. My / went from 18% to something like 30%. It is a 15GB partition. I did delete some other files, about 1GBs worth though. I didn't realize it was the compile at first. Sort of freaked me out. Hope you don't bork your rig. Dale :-) Jeff Cranmer wrote: I thought it was fully compiled, but I didn't check back before I closed the compile window (my bad). There are only 3.5GB free on my \var directory, so it's possible. I tried replacing the /var/tmp/portage directory with a symlink to my data drive to a directory owned by portage (group and user) on that drive, but portage failed to compile on that directory, quoting acces denied errors as it tried to create the necessary temporary directories. What is the correct way to set portage up to compile on another drive? Thanks Jeff On Fri, 2005-12-02 at 22:10 -0600, Dale wrote: Richard Fish wrote: If you are compiling from source, you will need _at least_ 4G of free space for PORTAGE_TMPDIR at the start of the merge. -Richard He is not kidding either. My /var is on my / partition and that puppy got big while compiling OOo. It's back to normal now though. It just needs the extra space during the compile is all. That is a similair error to what I got from KDE when it crashed on another rig. It makes sense at least. Dale :-) -- To err is human, I'm most certainly human. -- gentoo-user@gentoo.org mailing list -- To err is human, I'm most certainly human. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Openoffice 2 Install problems
On 12/3/05, Jeff Cranmer [EMAIL PROTECTED] wrote: I thought it was fully compiled, but I didn't check back before I closed the compile window (my bad). There are only 3.5GB free on my \var directory, so it's possible. Don't feel bad. I think in some cases the build and installation looks like it completes fine, even though it is only a partial build. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Openoffice 2 Install problems
On 12/3/05, Dale [EMAIL PROTECTED] wrote: Don't forget to remove the # though. May want to change it back afterwords too. You can change it temporarily in the environment: PORTAGE_TMPDIR=/mnt/data emerge openoffice -Richard -- gentoo-user@gentoo.org mailing list
[gentoo-user] Openoffice 2 Install problems
I've just upgraded to the latest version of openoffice It seems to be broken. When I start openoffice writer, I get the error /usr/lib/openoffice/program/javaldx: error while loading shared libraries: libuno_sal.so.3: cannot open shared object file: No such file or directory file_image_pagein: Invalid argument file_image_pagein: Invalid argument /usr/lib/openoffice/program/soffice.bin: error while loading shared libraries: libvcl680li.so: cannot open shared object file: No such file or directory Has anyone else experienced problems, or can otherwise help me resolve? Thanks Jeff
Re: [gentoo-user] Openoffice 2 Install problems
Richard Fish wrote: If you are compiling from source, you will need _at least_ 4G of free space for PORTAGE_TMPDIR at the start of the merge. -Richard He is not kidding either. My /var is on my / partition and that puppy got big while compiling OOo. It's back to normal now though. It just needs the extra space during the compile is all. That is a similair error to what I got from KDE when it crashed on another rig. It makes sense at least. Dale :-) -- To err is human, I'm most certainly human. -- gentoo-user@gentoo.org mailing list
