New Version. Corresponding ebuilds for openoffice and openoffice-bin needed. Reproducible: Always Steps to Reproduce:
Additional request: is there any chance of getting an ebuild for the unstable 1.9 branch? Openoffice is almost begging users to test it. It's only a small change to an ebuild every 2 weeks, and it works GREAT (well, downloaded the windows version), it's much better in importing word docs and everything.
Unfortunately, just renaming the 1.1.3 ebuild to 1.1.4 does not work. We need more ebuild-foo than that :-)
Already working at it, just give some time for testing... About 1.9.x: This is alpha-quality atm, I think we should wait at least until it goes beta...
i test OOo 1.9 with hacked ebuild but I do not really know if some flags for the building tools may changed?! it needs epm from http://www.easysw.com/epm/ and on packaging with that tool breaks here. I want to test if using the OOo epm patches for it may solve that but ooo.ximian.com is down and i do not find any mirror. Andreas do you know anything about changes in building from 1.1 to 1.9? PS gcc34 patches should apply on OOo 1.1.4 :)
*** Bug 75426 has been marked as a duplicate of this bug. ***
openoffice-bin 1.1.4 is already in portage @Hanno: Yes the gcc34 patches apply fine here, compiling the beast atm. Also: Didn't take a look on 1.9.x so really don't know
1.1.4 fails because of the new freetype, that's not good, cause the unmasking of freetype 2.1.9 most likely will also have broken the older OOos :( In file included from ./gcach_ftyp.hxx:65, from /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:69: ../../inc/glyphcache.hxx:96: warning: specialization of `template<class _Key> struct _STL::hash' in different namespace /var/tmp/portage/openoffice-1.1.4/work/solver/645/unxlngi4.pro/inc/stl/stl/_hash_fun.h:40: warning: from definition of `template<class _Key> struct _STL::hash' In file included from /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:80: /usr/include/freetype2/freetype/freetype.h:20:2: #error "`ft2build.h' hasn't been included yet!" /usr/include/freetype2/freetype/freetype.h:21:2: #error "Please always use macros to include FreeType header files." /usr/include/freetype2/freetype/freetype.h:22:2: #error "Example:" /usr/include/freetype2/freetype/freetype.h:23:2: #error " #include <ft2build.h>" /usr/include/freetype2/freetype/freetype.h:24:2: #error " #include FT_FREETYPE_H" /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx: In member function `long int FreetypeManager::AddFontDir(const String&)': /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:530: warning: comparison between `enum oslFileError' and `enum osl::FileBase::RC' /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx: In member function `int FreetypeServerFont::ApplyGlyphTransform(int, FT_GlyphRec_*) const': /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:906: warning: converting to `FT_Pos' from `double'/var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:908: warning: converting to `FT_Fixed' from `double' /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:909: warning: converting to `FT_Fixed' from `double' /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:910: warning: converting to `FT_Fixed' from `double' /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:911: warning: converting to `FT_Fixed' from `double' /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:917: warning: converting to `FT_Pos' from `double'/var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:918: warning: converting to `FT_Pos' from `double'/var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:919: warning: converting to `FT_Fixed' from `double' /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:920: warning: converting to `FT_Fixed' from `double' /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:921: warning: converting to `FT_Fixed' from `double' /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:922: warning: converting to `FT_Fixed' from `double' /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx: In member function `virtual void FreetypeServerFont::InitGlyphData(int, GlyphData&) const': /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:1101: warning: converting to `int' from `double' /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx: In member function `virtual ULONG FreetypeServerFont::GetKernPairs(ImplKernPairData**) const': /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx:1582: warning: comparison is always false due to limited range of data type distcc[30384] ERROR: compile /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs/gcach_ftyp.cxx on localhost failed dmake: Error code 1, while making '../../unxlngi4.pro/slo/gcach_ftyp.obj' ---* TG_SLO.MK *--- ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-1.1.4/work/vcl/source/glyphs !!! ERROR: app-office/openoffice-1.1.4 failed. !!! Function src_compile, Line 360, Exitcode 1 !!! Build failed! !!! If you need support, post the topmost build error, NOT this status message.
you may post ebuild and necessary files here to test :)
you may have a look at this: /usr/include/freetype2/freetype/freetype.h:20:2: #error "`ft2build.h' hasn't been included yet!" /usr/include/freetype2/freetype/freetype.h:21:2: #error "Please always use macros to include FreeType header files." /usr/include/freetype2/freetype/freetype.h:22:2: #error "Example:" /usr/include/freetype2/freetype/freetype.h:23:2: #error " #include <ft2build.h>" /usr/include/freetype2/freetype/freetype.h:24:2: #error " #include FT_FREETYPE_H" are these included like that? ignore me, if you checked already ;)
Created attachment 46722 [details] OOo 1.1.4 ebuild a working OOo-1.1.4 ebuild
Created attachment 46723 [details] freetype >=2.1.8 patch this should fix the compile problems with freetype-2.1.9
NOTES: to use the above build do the followings: 1) copy portage/app-office/openoffice/files/1.1.3 dir to portage/app-office/openoffice/files/1.1.4 dir 2) place vcl-freetype-2.1.8.patch in portage/app-office/openoffice/files/1.1.4 dir 3) place openoffice-1.1.4.ebuild in portage/app-office/openoffice dir 4) download the openoffice-1.1.4 source into distdir. 5) generate the digest as follows: cd /usr/portage/app-office/openoffice ebuild openoffice-1.1.4.ebuild digest 6) you may now proceed with the emerge hth
more NOTES: the above ebuild does not filter "-fomit-frame-pointer" and "-ftracer" compiler flags, as i have no problems with them, should you have issues with them just un-comment the following lines in the ebuild: #filter-flags "-fomit-frame-pointer" #filter-flags "-ftracer" hth happy compiling
Imad, unfortunately there are bugs in the gcc compiler. Those bugs are triggered by certain less common compilation options, possibly in the combination with certain architectures (pentium4 support is infamous for this). As not everyone runs the latest compilers, I think it is better to let the filters in. Openoffice is too fragile allready to add problems caused by compiler flags.
Hi, Imad your ebuild and patch worked for me after I changed one line in the ebuild due to missing "]" in line 192. Tank you :) Poly
so when will we see this in portage?
Sorry, did miss this for a few days as my mail account was down. Anyway: Just compiling and testing although I did take the patch from Mandrake: http://cvs.mandrakesoft.com/cgi-bin/cvsweb.cgi/~checkout~/SPECS/OpenOffice.org/openoffice-1.1-ft217.patch?rev=1.1.2.1&content-type=text/plain Will put it in portage soon, if everything works out fine
Created attachment 46996 [details] patch to resolve issue when compiling with USE="java" & gcc-3.4.c @Andrea, you may want to include, or a least take note of the attached patch. had issues compiling OOo with USE="java", and post gcc-3.4.3 compiler please see http://www.openoffice.org/issues/show_bug.cgi?id=39481 for more details, the attached patch solves it. hth happy new year
Ok, 1.1.4 is in portage, thanks to everyone for commenting and helping out. @Imad: With which version do this problems show up? Anyway: Will take a look at it
Oh, and: Closing
