Anyone have any clues as to why my 'emerge --update world' seems to fail
on mozilla with the following output:
>>> Unpacking ipc-1.1.2.tar.gz to /var/tmp/portage/mozilla-1.7.7/work
>>> Unpacking enigmail-0.91.0.tar.gz to /var/tmp/portage/mozilla-1.7.7/work
* Applying mozilla-stackgrowth.patch ... [ ok ]
* Applying mozilla-1.3-fix-RAW-target.patch ... [ ok ]
* Applying mozilla-hppa.patch ... [ ok ]
* Applying mozilla-1.7.3-4ft2.patch ... [ ok ]
* Patching smime to call perl from /usr/bin... [ ok ]
>>> Source unpacked.
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-www-client_-_mozilla-1.7.7-15107.log"
open_wr: /home2/digbyt/.history
--------------------------------------------------------------------------------
I assume that for some reason the mozilla configure balked at the
HISTFILE=/home2/digbyt/.history
that was left in my environment after I su'd to root.
An 'export HISTFILE=""' seemed to work around it, but I am not sure if
this should be reported as an 'emerge' bug or a 'mozilla' package bug.
Is there any reason why I should not run emerge after logging in as
myself and then 'su'ing? Are there guidelines on acceptable environment
settings that should be present when doing an emerge which I have
overlooked?
Regards,
DigbyT
--
Digby R. S. Tarvin [EMAIL PROTECTED]
http://www.digbyt.com
--
[email protected] mailing list
