| View previous topic :: View next topic |
| Author |
Message |
spool
n00b
Joined: 02 Feb 2006
Posts: 26
Location: UK
|
 Posted: Mon Apr 03, 2006 8:15 am Post subject: Any help I can provide... |
 |
|
Hi. Just thought you might appreciate another machine to test things on. I have a 1.5 Ghz. PowerBook.
If we can get 2.0.2 working, and if it won't crash when saving .docs my quality of life will improve immensely.
Good luck, and let me know if I can help. |
|
| Back to top |
|
 |
Cenrim
Tux's lil' helper
Joined: 04 Dec 2004
Posts: 142
Location: Germany
|
| Posted: Mon Apr 03, 2006 2:05 pm Post subject: |
|
|
tried oo-2.0.2 again yesterday (changelog said something about new patchset and stuff) but installing failed again..
right now I'm emerging 2.0.1-r1 ..
the linking of the installed 2.0.1 was broken because of an dev-libs/expat-update so I have to rebuild it anyway..
_________________
[/garbage] |
|
| Back to top |
|
|
fb
l33t
Joined: 08 Dec 2003
Posts: 636
Location: New Zealand
|
| Posted: Mon Apr 03, 2006 9:42 pm Post subject: |
|
|
| Cenrim wrote: | | tried oo-2.0.2 again yesterday (changelog said something about new patchset and stuff) but installing failed again.. |
My own compile of the same is not quite finished but after reading your results I wonder if I
should bother  . I guess that will be more stuff for the bug.
EDIT Yes it failed again same place. It's depressing. |
|
| Back to top |
|
|
Cenrim
Tux's lil' helper
Joined: 04 Dec 2004
Posts: 142
Location: Germany
|
| Posted: Tue Apr 04, 2006 9:35 pm Post subject: |
|
|
btw: 2.0.1-r1 fails at the same point as 2.0.2 
_________________
[/garbage] |
|
| Back to top |
|
|
fb
l33t
Joined: 08 Dec 2003
Posts: 636
Location: New Zealand
|
| Posted: Tue Apr 04, 2006 10:33 pm Post subject: |
|
|
| Cenrim wrote: | | btw: 2.0.1-r1 fails at the same point as 2.0.2 |
Now that becomes interesting. I shall package my current (working) install
and try that. My current build is from before the libcurl problem and is
labelled 2.0.1.3. In principle in 2.0.1-r1 they only removed the curl use flag
to prevent curl to be built internally (and I think I was building with -curl
anyway so no problem for me) - I wonder if it is related  . |
|
| Back to top |
|
|
fb
l33t
Joined: 08 Dec 2003
Posts: 636
Location: New Zealand
|
| Posted: Thu Apr 06, 2006 12:42 am Post subject: |
|
|
OK I did a quite barebone build of OOo-2.0.1-r1 (the only use falgs enabled where kde and xml)
and it failed at installation on registering components. However the components in question are not
the same than in the 2.0.2 case. | Code: | Thu Apr 6 10:25:11 2006 (01:00 min.)
######################################################
Registering python UNO components:
######################################################
SUCCESS: Source for types.rdb: /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/solver\
/680/unxlngppc.pro/bin/types.rdb
SUCCESS: Source for pyuno_services.rdb: /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-\
m1/solver/680/unxlngppc.pro/bin/pyuno_services.rdb
Systemcall: /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/solver/680/unxlngppc.pro\
/bin/regcomp -register -br /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/solver/680\
/unxlngppc.pro/bin/types.rdb -br /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/solv\
er/680/unxlngppc.pro/bin/pyuno_services.rdb -r /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/\
ooa680-m1/instsetoo_native/util/OpenOffice//services.rdb/en-US_inprogress_1/services.rdb -c vnd.openoffice.pymodu\
le:mailmerge -l com.sun.star.loader.Python 2>&1 |
ERROR: /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/solver/680/unxlngppc.pro/bin/\
regcomp -register -br /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/solver/680/unxl\
ngppc.pro/bin/types.rdb -br /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/solver/68\
0/unxlngppc.pro/bin/pyuno_services.rdb -r /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa68\
0-m1/instsetoo_native/util/OpenOffice//services.rdb/en-US_inprogress_1/services.rdb -c vnd.openoffice.pymodule:ma\
ilmerge -l com.sun.star.loader.Python 2>&1 |
Systemcall: /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/solver/680/unxlngppc.pro\
/bin/regcomp -register -br /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/solver/680\
/unxlngppc.pro/bin/types.rdb -br /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/solv\
er/680/unxlngppc.pro/bin/pyuno_services.rdb -r /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/\
ooa680-m1/instsetoo_native/util/OpenOffice//services.rdb/en-US_inprogress_1/services.rdb -c vnd.openoffice.pymodu\
le:pythonscript -l com.sun.star.loader.Python 2>&1 |
ERROR: /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/solver/680/unxlngppc.pro/bin/\
regcomp -register -br /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/solver/680/unxl\
ngppc.pro/bin/types.rdb -br /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/solver/68\
0/unxlngppc.pro/bin/pyuno_services.rdb -r /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa68\
0-m1/instsetoo_native/util/OpenOffice//services.rdb/en-US_inprogress_1/services.rdb -c vnd.openoffice.pymodule:py\
thonscript -l com.sun.star.loader.Python 2>&1 | |
The two errors are in the python components and concern "mailmerge" and "pythonscript". The error
in 2.0.2 is a bit more obscure and I don't think it is in pyuno.
After examination of the 2.0.1-r1 error log the failling component in 2.0.2 has been succesfully registered
in the 2.0.1-r1 case. It is a part of the uno components which are registered before the pyuno ones. |
|
| Back to top |
|
|
spool
n00b
Joined: 02 Feb 2006
Posts: 26
Location: UK
|
| Posted: Fri Apr 14, 2006 12:41 am Post subject: OOo bin... |
|
|
| Is there no progress? I really need a functioning OOo... does anyone have a binary of any version for ppc? |
|
| Back to top |
|
|
fb
l33t
Joined: 08 Dec 2003
Posts: 636
Location: New Zealand
|
| Posted: Fri Apr 14, 2006 1:53 am Post subject: Re: OOo bin... |
|
|
| spool wrote: | | Is there no progress? I really need a functioning OOo... does anyone have a binary of any version for ppc? |
I guess I have mine but it is tuned for G4 and I have nowhere to host it.
It was compiled with the following use flags: | Code: | | [ebuild U ] app-office/openoffice-2.0.2 [2.0.1] +binfilter +cairo -eds -firefox -gnome +gtk +java +kde -ldap -mono -mozilla +xml |
And my CFLAGS are "-O2 -mcpu=7450 -pipe -maltivec -mabi=altivec -mpowerpc-gfxopt -fsigned-char -frename-registers -fweb -fno-strict-aliasing".
Don't know if that would help you. |
|
| Back to top |
|
|
spool
n00b
Joined: 02 Feb 2006
Posts: 26
Location: UK
|
| Posted: Fri Apr 14, 2006 2:07 am Post subject: ??? Do you mean you actually got 2.0.2 to compile? |
|
|
Wow, it worked? My hardrive space is so low I figured it wasn't worth attempting again, but since you actually got it to compile maybe I'll try myself.
Thanks. |
|
| Back to top |
|
|
jaeger63
n00b
Joined: 08 Apr 2006
Posts: 38
Location: Gatineau, Quebec
|
| Posted: Fri Apr 14, 2006 2:48 am Post subject: Re: OOo bin... |
|
|
| fb wrote: |
I guess I have mine but it is tuned for G4 and I have nowhere to host it.
It was compiled with the following use flags: | Code: | | [ebuild U ] app-office/openoffice-2.0.2 [2.0.1] +binfilter +cairo -eds -firefox -gnome +gtk +java +kde -ldap -mono -mozilla +xml |
And my CFLAGS are "-O2 -mcpu=7450 -pipe -maltivec -mabi=altivec -mpowerpc-gfxopt -fsigned-char -frename-registers -fweb -fno-strict-aliasing".
Don't know if that would help you. |
Did this version fix the crashing while saving .doc problem? If so, I'll try compiling it on my G5 too. |
|
| Back to top |
|
|
fb
l33t
Joined: 08 Dec 2003
Posts: 636
Location: New Zealand
|
| Posted: Fri Apr 14, 2006 4:58 am Post subject: No I didn't compile 2.0.2 |
|
|
| spool wrote: | Wow, it worked? My hardrive space is so low I figured it wasn't worth attempting again, but since you actually got it to compile maybe I'll try myself.
Thanks. |
No I didn't! It was just a quick emerge -pv to show the flags I use. You will notice that on
the left it says "U" for upgrade not "R" for rebuild. The version number I have currently
running is 2.0.1. And it works for me. I recommand 4GB to compile it - the ebuild says
4 to 6 GB.
For jaeger63: I am aware of this bug but I don't remember suffering from it. I cannot really
try anything as my ppc machine is my work machine and the uni is on holiday until wednesday.
I can connect and look at stuff remotely but using openoffice over ssh may be heavy (VNC is not
an option). |
|
| Back to top |
|
|
btlee
Apprentice
Joined: 03 Sep 2004
Posts: 168
Location: San Francisco
|
| Posted: Mon Apr 17, 2006 8:53 am Post subject: |
|
|
How about getting binary from fedora 5?
AFAIK, fedora 5 has a OO 2.0.2, but it runs on glibc 2.4.
I think that this means we can use the binary if your gentoo runs on glibc 2.4.
Of course, you may be unsatisfactory because you didn't build it on your ppc,
but, still I think that this is one of realistic alternatives.
_________________
AMD64 3200+, 2G/160G+250G
DELL 700m, 1.8GHz, 2G/80G
iBook G3-500Mhz, 640M/100G |
|
| Back to top |
|
|
fb
l33t
Joined: 08 Dec 2003
Posts: 636
Location: New Zealand
|
| Posted: Mon Apr 17, 2006 10:13 pm Post subject: |
|
|
| btlee wrote: | How about getting binary from fedora 5?
AFAIK, fedora 5 has a OO 2.0.2, but it runs on glibc 2.4.
I think that this means we can use the binary if your gentoo runs on glibc 2.4.
Of course, you may be unsatisfactory because you didn't build it on your ppc,
but, still I think that this is one of realistic alternatives. |
I guess that could be a solution for some people - I have gcc 4.1.0 with glibc 2.3.6
(You need at least glibc 2.3.6 to compile gcc4.1.0 and you need gcc4.1.0 to compile
glibc 2.4 so you have to do some compile work there). On the bright side using
gcc4.1.0 has been overall a good experience, a few package are broken, but most
of the time going to ~ppc solve the problem. I don't know yet about moving
to glibc 2.4 but it should be OK, especially considering that ppc glibc have been ntplonly
for quite some time now. |
|
| Back to top |
|
|
spool
n00b
Joined: 02 Feb 2006
Posts: 26
Location: UK
|
| Posted: Wed Apr 19, 2006 4:57 pm Post subject: What about fink? |
|
|
I have fink on my OS X install, and OOo 2.0.2 is in the package list (sadly no bin...). Could I cross compile on a different OS? I've never tried that before... just wondering if anyone knows if it would work.
Otherwise, are there any major repercussion for upgrading both glibc and gcc? Do I only have to compile those, and possibly deal with future (broken) compilations, or will it possibly break things that already work (besides themselves)? Also if there are any particular benefits that might outweigh downsides...
Thanks. |
|
| Back to top |
|
|
fb
l33t
Joined: 08 Dec 2003
Posts: 636
Location: New Zealand
|
| Posted: Wed Apr 19, 2006 10:39 pm Post subject: Re: What about fink? |
|
|
| spool wrote: | | I have fink on my OS X install, and OOo 2.0.2 is in the package list (sadly no bin...). Could I cross compile on a different OS? I've never tried that before... just wondering if anyone knows if it would work. |
In theory yes. In practice you need to install a cross-compiler which, I gather, can be a daunting task and
I don't know if you have the necessary tools in fink for that. On a point of details OSX use Mach-O
(someone correct me if I am wrong in the spelling) while linux use ELF for their respective executable
files. The differences are significant and you won't get (easily) one format executing on the wrong platform.
And that's just one issue. If you think you can get around the problem in linux by just using the version in fink
then the answer is definitely no, once your cross-platform tool chain is in place it is likely that you will get
into the same kind of troubles than in linux ppc when you try to compile for that target.
| spool wrote: | Otherwise, are there any major repercussion for upgrading both glibc and gcc? Do I only have to compile those, and possibly deal with future (broken) compilations, or will it possibly break things that already work (besides themselves)? Also if there are any particular benefits that might outweigh downsides...
Thanks. |
A few program don't work at all at the moment with gcc4.1.0, some need a version bump that you can
get from using ~ppc. In a few case like scilab a version supporting gcc4.1.0 is not in portage yet but is
released upstream (in this particular case there is an ebuild in a bug if I remember correctly).
But overall the problems are few and disapearing fast. I am not sure if their are issues associated with the use
of glibc2.4, the only one that concerns some people is the fact that it is now nptl only but ppc has been
nptl only for a while now. |
|
| Back to top |
|
|
fb
l33t
Joined: 08 Dec 2003
Posts: 636
Location: New Zealand
|
| Posted: Sun Apr 23, 2006 5:37 am Post subject: |
|
|
suka updated the ebuild to openoffice2.0.2-r2. I tried to build again this time with
gcc4.1.0 (as my system is now almost completly compiled with gcc4.1.0) and without
java (to avoid) problems. It still fails at install time on the registration of some components.
They are a bit different from what I remember. First there is a UNO component: | Code: | register component 'typemgr.uno.so' in registry '/var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/inst\
setoo_native/util/OpenOffice//services.rdb/en-US_inprogress_1/services.rdb' succesful!
ERROR: /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.pro/bin/regcomp -registe\
r -r /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//services.rdb/e\
n-US_inprogress_1/services.rdb -c 'libscriptframe.so;libsd680lp.so;slideshow.uno.so;libsdbc2.so;libsdd680lp.so;security.uno.so;li\
bprotocolhandler680lp.so;libsfx680lp.so;simplereg.uno.so;servicemgr.uno.so;libsot680lp.so;libspell680lp.so;libspl680lp.so;libsrtr\
s1.so;streams.uno.so;libsvt680lp.so;svtmisc.uno.so;libsvx680lp.so;libtextconversiondlgs680lp.so;libsw680lp.so;libdtransX11680lp.s\
o;syssh.uno.so;localebe1.uno.so;typeconverter.uno.so;typemgr.uno.so' 2>&1 |
Systemcall: /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.pro/bin/regcomp -re\
gister -r /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//services.\
rdb/en-US_inprogress_1/services.rdb -c 'textinstream.uno.so;libtk680lp.so;textoutstream.uno.so;libtvhlp1.so;libucb1.so;libucpchel\
p1.so;libucpdav1.so;libucpfile1.so;libucpftp1.so;libucphier1.so;libucppkg1.so;ucptdoc1.uno.so;ucpexpand1.uno.so;uriproc.uno.so;li\
butl680lp.so;libuui680lp.so;uuresolver.uno.so;libvcl680lp.so;libxcr680lp.so;libxmx680lp.so;libxof680lp.so;libxo680lp.so;libxstor.\
so;libxsltdlg680lp.so;libxsltfilter680lp.so' 2>&1 |
register component 'textinstream.uno.so' in registry '/var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2\
/instsetoo_native/util/OpenOffice//services.rdb/en-US_inprogress_1/services.rdb' succesful!
register component 'libtk680lp.so' in registry '/var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/insts\
etoo_native/util/OpenOffice//services.rdb/en-US_inprogress_1/services.rdb' succesful!
|
Then there are two pyUNO components: | Code: | Sun Apr 23 17:18:46 2006 (01:03 min.)
######################################################
Registering python UNO components:
######################################################
SUCCESS: Source for types.rdb: /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.p\
ro/bin/types.rdb
SUCCESS: Source for pyuno_services.rdb: /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/un\
xlngppc.pro/bin/pyuno_services.rdb
Systemcall: /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.pro/bin/regcomp -re\
gister -br /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.pro/bin/types.rdb -br\
/var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.pro/bin/pyuno_services.rdb -r /\
var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//services.rdb/en-US_i\
nprogress_1/services.rdb -c vnd.openoffice.pymodule:mailmerge -l com.sun.star.loader.Python 2>&1 |
ERROR: /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.pro/bin/regcomp -registe\
r -br /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.pro/bin/types.rdb -br /var\
/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.pro/bin/pyuno_services.rdb -r /var/t\
mp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//services.rdb/en-US_inprog\
ress_1/services.rdb -c vnd.openoffice.pymodule:mailmerge -l com.sun.star.loader.Python 2>&1 |
Systemcall: /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.pro/bin/regcomp -re\
gister -br /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.pro/bin/types.rdb -br\
/var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.pro/bin/pyuno_services.rdb -r /\
var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//services.rdb/en-US_i\
nprogress_1/services.rdb -c vnd.openoffice.pymodule:pythonscript -l com.sun.star.loader.Python 2>&1 |
ERROR: /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.pro/bin/regcomp -registe\
r -br /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.pro/bin/types.rdb -br /var\
/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/solver/680/unxlngppc.pro/bin/pyuno_services.rdb -r /var/t\
mp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//services.rdb/en-US_inprog\
ress_1/services.rdb -c vnd.openoffice.pymodule:pythonscript -l com.sun.star.loader.Python 2>&1 |
Moved directory from /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/instsetoo_native/util/OpenOffice\
//services.rdb/en-US_inprogress_1 to /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/instsetoo_native\
/util/OpenOffice//services.rdb/en-US_witherror_1
Removing directory /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//\
zip/en-US
Removing directory /var/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.7/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//\
services.rdb/en-US_witherror_1
***************************************************************
ERROR: Could not register all components!
in function: create_services_rdb
***************************************************************
|
The ebuild was started remotely with a comand | Code: | | nohup emerge openoffice & |
so I have a complete log of the build inside the nohup.out file. I may try to have a look
at it to see if I can find the source of the problem. |
|
| Back to top |
|
|
fb
l33t
Joined: 08 Dec 2003
Posts: 636
Location: New Zealand
|
| Posted: Sun Jun 18, 2006 11:14 pm Post subject: |
|
|
Hi,
I just thought I would resurect this thread to mention that I was succesful
at last in emerging openoffice-2.0.2-r2. My config is now:
gcc4.1.1 glibc-2.4-r3 xorg-x11-7.1.
Note that after updating to glibc-2.4 I had to update to xorg-x11-7.1,
the 6.8.2-r7 release wouldn't build (more precisely it wouldn't build opengl)
and for some strange it was breaking STLport in openoffice.
Once I had upgraded to 7.1 the openoffice version of STLport built without
a itch.
To prevent the installation failure problem I compiled with CFLAGS=""
and CXXFLAGS=$CFLAGS and I also emptied my ccache which may help.
My normal CFLAGS seem to cause the installation failure, and using ccache
may actually hide this problem (ie we you try to build again with reduced
CFLAGS it still breaks) but I am not completly sure.
I did the emerge with the following USE flags:
| Code: | | [ebuild R ] app-office/openoffice-2.0.2-r2 USE="cairo firefox gtk kde xml -binfilter -eds -gnome -java -ldap -mono -mozilla" |
|
|
| Back to top |
|
|
|
Gentoo on PPC
