Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 109306 - Open Office 2.0.rc2-r2 compile fails trying to apply non-existent patches
Summary: Open Office 2.0.rc2-r2 compile fails trying to apply non-existent patches
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Office Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-14 14:49 UTC by Thomas S. Howard
Modified: 2005-10-15 19:47 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas S. Howard 2005-10-14 14:49:16 UTC
First patch failure
-------------------------------------------------------------------------------
/var/tmp/portage/openoffice-2.0.0_rc2/work/ooo-build-2.0.rc2-2/patches/apply.pl
/var/tmp/portage/op enoffice-2.0.0_rc2/work/ooo-build-2.0.rc2-2/patches/OOO_2_0
/var/tmp/portage/openoffice-2.0.0_rc2/w ork/ooo-build-2.0.rc2-2/build/ooo680-m2
$FLAGS --tag=ooo680-m2 ;
Execute with  for distro(s) 'Gentoo64 Localize'
PATCHPATH => .:../src680:../evo2:../vba:../mono:../64bit:../cairo


** Error ** - Can't find file cws-ooo64bit02.2005-04-19-math-h.diff in patch
path '.:../src680:../e vo2:../vba:../mono:../64bit:../cairo'


make: *** [stamp/patch.apply] Error 2

!!! ERROR: app-office/openoffice-2.0.0_rc2 failed.
!!! Function src_compile, Line 197, Exitcode 2
!!! Build failed
-------------------------------------------------------------------------------

Second Patch failure
-------------------------------------------------------------------------------
/var/tmp/portage/openoffice-2.0.0_rc2/work/ooo-build-2.0.rc2-2/patches/apply.pl
/var/tmp/portage/openoffice-2.0.0_rc2/work/ooo-build-2.0.rc2-2/patches/OOO_2_0
/var/tmp/portage/openoffice-2.0.0_rc2/work/ooo-build-2.0.rc2-2/build/ooo680-m2
$FLAGS --tag=ooo680-m2 ;
Execute with  for distro(s) 'Gentoo64 Localize'
PATCHPATH => .:../src680:../evo2:../vba:../mono:../64bit:../cairo


** Error ** - Can't find file buildfix-64bit-sc.diff in patch path
'.:../src680:../evo2:../vba:../mono:../64bit:../cairo'


make: *** [stamp/patch.apply] Error 2

!!! ERROR: app-office/openoffice-2.0.0_rc2 failed.
!!! Function src_compile, Line 197, Exitcode 2
!!! Build failed


Reproducible: Always
Steps to Reproduce:
1.ebuild  /usr/portage/app-office/openoffice/openoffice-2.0.rc2-2.ebuild compile
2. edit
/var/tmp/portage/openoffice-2.0.0_rc2/work/ooo-build-2.0.rc2-2/patches/OOO_2_0/apply
comment out line #790
3. Repeat step 1


Actual Results:  
compile fails 

Expected Results:  
Not apply patches that don't exist

The fix is simple, and actually needs to be partially applied to repeat all the
errors. To fix edit the file:

/var/tmp/portage/openoffice-2.0.0_rc2/work/ooo-build-2.0.rc2-2/patches/OOO_2_0/apply

comment out line #790
comment out line #799
Comment 1 Andreas Proschofsky (RETIRED) gentoo-dev 2005-10-14 16:27:28 UTC
I fail to see, how the build failing with a not supported (and not keyworded)
architecture could be a bug. OOo 2.0 does NOT build and work with AMD64 atm.
Nothing to add here
Comment 2 Thomas S. Howard 2005-10-14 16:44:41 UTC
(In reply to comment #1)
> I fail to see, how the build failing with a not supported (and not keyworded)
> architecture could be a bug. OOo 2.0 does NOT build and work with AMD64 atm.
> Nothing to add here

Yes, but there is a binary package and active work is being done to port it to
AMD64, so isn't it useful to know about compile errors on that architecture?
Especially since these two patches are specifically for the AMD64 platform?
Comment 3 Andreas Proschofsky (RETIRED) gentoo-dev 2005-10-15 00:27:56 UTC
According to the upstream developers the AMD64-port will take at least another 6
months to be finished, so it is rather useless to correct temporary trivial bugs
in the build system of an hard masked RC2.

If you want to help with AMD64-porting please report bugs upstream, in this
case, this is a "problem" in ooo-build, so the correct place would be:

https://bugzilla.novell.com/index.cgi

Though most likely this will already have been fixed by the corresponding
developers (as they are working with ooo-build), so it is a little bit useless.

Comment 4 Thomas S. Howard 2005-10-15 19:47:54 UTC
Alright, thanks for clearing that up. Also, I didn't realize how relatively
ancient the native x86_64 binary builds are.