View previous topic :: View next topic |
Author |
Message |
dE_logics Advocate
Joined: 02 Jan 2009 Posts: 2253 Location: $TERM
|
Posted: Tue Dec 04, 2012 1:06 pm Post subject: Anyone with Graphite + libreoffice? |
|
|
Can you please try opening/saving a *x (MS 'Open' XML 2007/2010) to confirm a bug --
https://bugs.gentoo.org/show_bug.cgi?id=429766
Also post your graphite flags. Mine are -floop-interchange -floop-strip-mine -floop-block -fgraphite-identity. _________________ My blog |
|
Back to top |
|
|
gringo Advocate
Joined: 27 Apr 2003 Posts: 3793
|
Posted: Wed Dec 05, 2012 11:49 am Post subject: |
|
|
cant reproduce it here, havent updated to 3.6.4.3 yet, and im using following flags : -floop-interchange -floop-strip-mine -floop-block.
Im not sure if graphite really matters here : doesnt the ebuild actually filter them out ?
cheers |
|
Back to top |
|
|
dE_logics Advocate
Joined: 02 Jan 2009 Posts: 2253 Location: $TERM
|
Posted: Wed Dec 05, 2012 3:00 pm Post subject: |
|
|
No. That's what I suggested.
So this maybe a problem with -floop-block -fgraphite-identity
I'll try this out. _________________ My blog |
|
Back to top |
|
|
jasn Guru
Joined: 05 May 2005 Posts: 439 Location: Maryland, US
|
Posted: Wed Dec 05, 2012 9:20 pm Post subject: |
|
|
I can confirm that on my system, enabling graphite CFGLAGs and then emerging the latest libreoffice, I get the same behavior pointed out in the bug report. My steps were;
1) enabled the graphite CFLAGs, -floop-interchange -floop-strip-mine -floop-block -fgraphite-identity
2) re-emerged gcc-4.7.2, glibc-2.16.0, binutils-2.23.1 and gcc-4.7.2 again
3) re-emerged the current libreoffice-l10n-3.6.3.2 and libreoffice-3.6.4.3
4) I then tried to open Coca_Cola_pl_c_UK.docx in Libreoffice Writer, and it wouldn't open at all. First gave the message that the file was corrupted and Libreoffice could try to repair the file. Clicking on yes, then displayed the error message that the file was corrupted and could not be opened.
Removing all of the graphite CFLAGs from my /etc/portage/make.conf, and then re-emerging gcc, glibc, binutils, gcc, libreoffice-l10n, and libreoffice, allowed me to open the file correctly.
Good Luck.. |
|
Back to top |
|
|
dE_logics Advocate
Joined: 02 Jan 2009 Posts: 2253 Location: $TERM
|
Posted: Fri Dec 07, 2012 3:30 pm Post subject: |
|
|
Thanks, the bug is now confirmed, now I'll see exactly what flag. _________________ My blog |
|
Back to top |
|
|
|