Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 214575 - >=app-office/openoffice-2.4.0-rc5 - system-cairo support is broken
Summary: >=app-office/openoffice-2.4.0-rc5 - system-cairo support is broken
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: Other Linux
: High normal (vote)
Assignee: Gentoo Office Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-24 19:04 UTC by Matt
Modified: 2008-03-24 20:50 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 Matt 2008-03-24 19:04:46 UTC
there are 2 errors:

1.) gtk cairo-support of ebuild isn't supported in the package (gives an error message)
2.) the build-process tries to fetch cairo-1.4.0 & fails

Reproducible: Always

Steps to Reproduce:
1.try to emerge openoffice
2.
3.

Actual Results:  
fail to emerge openoffice

Expected Results:  
it should pass every step during emerge but fails already at the beginning ;)

Copying cairo into tree
Looking for /var/tmp/portage/app-office/openoffice-2.4.0_rc5/distdir/cairo-1.4.10.tar.gz ... missing the /var/tmp/portage/app-office/openoffice-2.4.0_rc5/distdir/cairo-1.4.10.tar.gz archive; run './download'
make: *** [/var/tmp/portage/app-office/openoffice-2.4.0_rc5/work/ooo/build/OOH680_m11/unpack] Error 1
Comment 1 Andreas Proschofsky (RETIRED) gentoo-dev 2008-03-24 20:31:08 UTC
I did an update to the ebuild today, could you resync and try again? Also I don't quite get what you mean with point 1)
Comment 2 Matt 2008-03-24 20:50:48 UTC
FINALLY !

thanks :)

point 1) didn't appear anymore, if I recall right it said that it doesn't contain cairo-support ???

perhaps just a bogus error-message ? ;)

it's building right now with gcc-4.2.3 & hardened under amd64,

I'll let you know if I encounter any other problem,

I'm closing the bug for now :)

fix == re-syncing portage-tree