openoffice-ximian won't compile: boost_1_27_0/tools/build/test/test_nt_line_length.jam boost_1_27_0/tools/build/test/tree.py boost_1_27_0/tools/build/test/unit-tests.jam boost_1_27_0/tools/build/TODO.txt boost_1_27_0/tools/build/tru64cxx-tools.jam boost_1_27_0/tools/build/tru64cxx65-tools.jam boost_1_27_0/tools/build/unit-tests.jam boost_1_27_0/tools/build/vacpp-tools.jam boost_1_27_0/tools/make-cputime-page.pl make writeable... cd ./unxlngi4.pro/misc/build && cat ../../../boost_1_27_0.patch | patch -b -p2 && touch so_patched_ooo_boost patch: **** File boost_1_27_0/boost/config/compiler/gcc.hpp seems to be locked by somebody else under Perforce dmake: Error code 2, while making './unxlngi4.pro/misc/build/so_patched_ooo_boost' ---* TG_SLO.MK *--- ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-ximian-1.1.51-r1/work/oo_1.1_src/boost !!! ERROR: app-office/openoffice-ximian-1.1.51-r1 failed. !!! Function src_compile, Line 362, Exitcode 1 !!! Build failed! root@tinny:/var/tmp/portage/openoffice-ximian-1.1.51-r1/work/oo_1.1_src/boost/unxlngi4.pro/misc/build/boost_1_27_0/boost/config/compiler$ ls -la gcc.hpp -rw-r--r-- 1 scott 544 1911 Feb 7 2002 gcc.hpp
Could you attach the full build log?
No new info provided so closing this
I'm having the same trouble as the original submitter with openoffice-1.1.4-r1. I have perforce installed on my system. This message seems to describe the problem and the solution: http://lists.gllug.org.uk/pipermail/gllug/2004-June/044816.html Basically, gnu patch is "too smart for its own good", and is trying to pull a fix from perforce automagically. Setting the PATCH_GET environment variable to 0 "fixes" the problem. I realize this isn't strictly speaking a gentoo problem; its a subtle interaction between patch, openoffice, and perforce. But since it is never the desired behavior to have patch try and check perforce when emerging openoffice, would the openoffice team be willing to set the PATCH_GET environment variable as part of the ebuild file? Or perhaps this should be part of ebuild itself...
