After 12.5 hours . . . . . . . /mnt/huge/tmp/portage/openoffice-1.0.1/image/opt/OpenOffice.org1.0.1/program/libsvg641li.so /mnt/huge/tmp/portage/openoffice-1.0.1/image/opt/OpenOffice.org1.0.1/program/liblth641li.so /mnt/huge/tmp/portage/openoffice-1.0.1/image/opt/OpenOffice.org1.0.1/program/gnomeint >>> Completed installing into /mnt/huge/tmp/portage/openoffice-1.0.1/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-openoffice-1.0.1-12320.log" open_wr: /dev/dri/card0 open_wr: /dev/dri/card1 open_wr: /dev/dri/card2 open_wr: /dev/dri/card3 open_wr: /dev/dri/card4 open_wr: /dev/dri/card5 open_wr: /dev/dri/card6 open_wr: /dev/dri/card7 open_wr: /dev/dri/card8 open_wr: /dev/dri/card9 open_wr: /dev/dri/card10 open_wr: /dev/dri/card11 open_wr: /dev/dri/card12 open_wr: /dev/dri/card13 open_wr: /dev/dri/card14 open_wr: /share/psprint/pspfontcache open_wr: /user/psprint/pspfontcache -------------------------------------------------------------------------------- I'm going to try again tonight, as often these errors are not repeated on subsequent attempts.
Tested again on a 1.4 machine - same problem
Created attachment 4677 [details, diff] openoffice-dri.patch I just ran across this problem today, too. I've attached a really minor patch to the ebuild which fixes the problem; it seems that everything still works okay. Basically all I changed was adding an "addpredict" line for "/dev/dri"
I had exactly the same problem. I can confirm that the patch above helped me to get OpenOffice to emerge and it works. Thanks Cj Kucera Can this be submitted?
works for me too
I also got an access violation on gentoo 1.4, but only the last two entries: open_wr: /share/psprint/pspfontcache open_wr: /user/psprint/pspfontcache Of course that after two days compiling I bypassed emerge and copied everything in /var/tmp/portage/openoffice-1.0.1-r1/image into / ...
*** Bug 7965 has been marked as a duplicate of this bug. ***
*** Bug 8383 has been marked as a duplicate of this bug. ***
*** Bug 7720 has been marked as a duplicate of this bug. ***