When I emerge openoffice I get an error while compiling (apparently while patching). I looked into the contents of </var/tmp/portage/openoffice-1.1.4-r1/temp/gcc34.patch.bz2-16006.out> and found that the failures start as from the point in the code where Hunk # 1 FAILED at 122... Here is a part of that code (I place ellipsis and line space to fast forward to latter errors which I presume are related) OUTPUT of /var/tmp/portage/openoffice-1.1.4-r1/temp/gcc34.patch.bz2-16006.out: line 207/6608 (3%), col 1/49 (2%), char 10034/294418 (3%) patching file sw/source/ui/inc/glossary.hxx patching file sw/source/core/undo/undraw.cxx patching file sw/source/core/docnode/ndsect.cxx patching file sw/source/core/docnode/ndtbl.cxx Hunk #1 succeeded at 3321 (offset 8 lines). patching file sw/source/core/bastyp/calc.cxx patching file sw/source/ui/wizard/wizpage.hxx patching file sw/source/ui/wizard/wizag.hxx Hunk #1 FAILED at 122. Hunk #2 FAILED at 158. 2 out of 2 hunks FAILED -- saving rejects to file sw/source/ui/wizard/wizag.hxx.rej patching file sw/source/ui/wizard/wizmulti.cxx patching file sw/source/filter/ww1/w1class.hxx patching file dbaccess/source/core/dataaccess/SharedConnection.hxx patching file comphelper/inc/comphelper/types.hxx patching file cppu/inc/com/sun/star/uno/Any.hxx patching file cppu/inc/com/sun/star/uno/Reference.hxx patching file cppu/inc/com/sun/star/uno/Sequence.hxx patching file cppu/inc/com/sun/star/uno/Type.hxx patching file cppu/inc/uno/lbnames.h patching file cppu/inc/uno/mapping.hxx patching file cppu/test/surrogate.hxx patching file cppu/test/testcppu.cxx patching file cppu/test/test_di.cxx =========================== PIPE_COMMAND: bzip2 -dc /usr/portage/app-office/openoffice/files/1.1.4/gcc34.patch.bz2 > /var/tmp/portage/openoffice-1.1.4-r1/temp/16006.pa$ PATCH COMMAND: patch -p1 -g0 < /var/tmp/portage/openoffice-1.1.4-r1/temp/16006.patch =========================== can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- connectivity/source/drivers/jdbc/Connection.cxx.conn31464 2003-06-06 12:50:29.000000000 +0200 |+++ connectivity/source/drivers/jdbc/Connection.cxx 2004-07-21 20:56:18.649939969 +0200 -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 32 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- connectivity/source/drivers/jdbc/DatabaseMetaData.cxx.conn31464 2003-04-24 15:20:00.000000000 +0200 |+++ connectivity/source/drivers/jdbc/DatabaseMetaData.cxx 2004-07-21 20:56:18.657940037 +0200 -------------------------- No file to patch. Skipping patch. 52 out of 52 hunks ignored can't find file to patch at input line 505 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- connectivity/source/drivers/jdbc/ResultSet.cxx.conn31464 2003-04-24 15:21:49.000000000 +0200 |+++ connectivity/source/drivers/jdbc/ResultSet.cxx 2004-07-21 20:56:18.667940121 +0200 -------------------------- No file to patch. Skipping patch. 7 out of 7 hunks ignored can't find file to patch at input line 579 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- connectivity/source/drivers/jdbc/SQLException.cxx.conn31464 2003-04-24 15:22:09.000000000 +0200 |+++ connectivity/source/drivers/jdbc/SQLException.cxx 2004-07-21 20:56:18.669940138 +0200 -------------------------- ... No file to patch. Skipping patch. 5 out of 5 hunks ignored can't find file to patch at input line 1425 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- psprint/source/helper/ppdparser.cxx.gcc341psprint 2004-07-14 08:55:32.562784456 +0200 |+++ psprint/source/helper/ppdparser.cxx 2004-07-14 09:57:21.569795875 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 1436 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- sablot/Sablot-0.52.patch.orig 2003-08-05 11:41:11.000000000 +0200 |+++ sablot/Sablot-0.52.patch 2004-06-04 17:42:27.000000000 +0200 -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 1514 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- sal/inc/osl/mutex.hxx.gcc341sal 2003-04-04 19:10:54.000000000 +0200 |+++ sal/inc/osl/mutex.hxx 2004-07-14 09:11:23.993771522 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 1527 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- sal/inc/rtl/instance.hxx.gcc341saltypo 2003-05-22 11:32:56.000000000 +0200 |+++ sal/inc/rtl/instance.hxx 2004-07-14 09:35:39.841707299 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 1538 Perhaps you used the wrong -p or --strip option? The text leading up to this was: And so on and so forth... Reproducible: Didn't try Steps to Reproduce: 1.emerge openoffice 2. 3. Actual Results: Received this notice: " * Failed Patch: gcc34.patch.bz2 ! * ( /var/tmp/portage/openoffice-1.1.4-r1/temp/16006.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/openoffice-1.1.4-r1/temp/gcc34.patch.bz2-16006.out !!! ERROR: app-office/openoffice-1.1.4-r1 failed. !!! Function epatch, Line 358, Exitcode 0 !!! Failed Patch: gcc34.patch.bz2! !!! If you need support, post the topmost build error, NOT this status message. " Expected Results: Resulted in an installed version of OpenOffice. Running the root console from a user inside of KDE. Opened programs: Mozilla, XMMS, Home, and Gaim...
Works for me, are you sure, that you have enough free diskspace. Also try to delete gcc34.patch.bz2 from distfiles and try again. Also we need the output of your "emerge info", without this, there is nothing we can do...
Works here, most likely a local problem, no feedback, closing
