Apache OpenOffice (AOO) Bugzilla – Issue 25252
Solaris x86 gcc port
Last modified: 2005-02-13 16:33:03 UTC
This is a patchs to build on Solaris x86 with gcc against cws_srx645_ooo111fix3.
Created attachment 12994 [details] Solaris x86 gcc patches
Adding me to CC.
Change issue type to patch.
Created attachment 13466 [details] set_soenv.in add Solaris gcc environment patch
Created attachment 13467 [details] configure.in GNU ld check patch
Created attachment 13468 [details] unx.mk add include unxsogi.mk patch
Created attachment 13469 [details] unxsogi.mk new file patch
Created attachment 13470 [details] stlport global scope patch
Created attachment 13471 [details] bridge build.lst add cpp_uno patch
Created attachment 13472 [details] cpp_uno gcc3_solaris_intel new files patch
Created attachment 13473 [details] cppy static_types.cxx stdargs patch
Created attachment 13474 [details] javaldx libstdc++ patch
Created attachment 13475 [details] icu gcc linker patch
Created attachment 13476 [details] nas if HasSunC fix patch
Created attachment 13477 [details] psprint GNU ld mapfile patch
Created attachment 13478 [details] Python-2.2.2 gethostbyname declaration patch
Created attachment 13479 [details] ttime.cxx altzone patch
Created attachment 13480 [details] i18n_wrp.cxx stdarg.h patch
Created attachment 13481 [details] Solaris gcc stachtrace assmbller patch
I cleaned up the patches that I had registered to this issue. config_office-set_soenv.in-add_solarisgccenv.patch.20040227: This patch modify some envirment variables in order to build OOo on Solaris x86 system.CC, COM, CVER, and so on. config_office-configure.in-solaris_gnuld_check.patch: It is necessary for gcc to use GNU ld on Solaris. This patch add a functionarity to check whether gcc uses GNU ld or not. solenv-inc-unxsogi.mk-add_solaris_x86_new_include_file.patch This patch add unxsogi.mk under solenv/inc that is include file for Solaris x86 gcc build. solenv-inc-unx.mk-add_solarisigccinclude.patch: This patch modifies unx.mk to include unxsogi.mk stlport-STLport-4.5.patch-solaris_gcc_global_cstd.patch Some multibyte and wide char functions are in global scope on Solaris x86 gcc environment. This patch modifies STLport-4.5/stl/config/stl_gcc.h to fix build error. bridges-prj-build.lst-cpp_uno_gcc3_solaris_intel.patch bridges-source-cpp_uno-gcc3_solaris_intel-newfiles.patch These patches add CPP UNO for gcc3_solaris_intel environment. These are copies of gcc3_linux_intel cppu-source-typelib-static_types.cxx-solarisgcc_stdarg.patch vcl-unx-source-app-i18n_wrp.cxx-solarisgcc_stdarg.patch It is necessary to use <stdarg.h> instead of <varargs.h> with gcc3. These patches modify #ifdef directive for gcc to include <stdarg.h> under Solaris gcc environment. desktop-source-javaldx-makefile.mk-add_libstdc++_link.patch.20040227 icu-icu-2.2.patch_solaris_gcc_linker.patch.20040227 These patches modify files to link libstdc++ in order to solve symbol problems. nas-nas-1.6.patch-ifHasSunC.patch It is necessary to use "#if HasSunC" instead of "#ifdef HasSunC". This patch resolves this problem. psprint-util-makefile.mk-mapfile_gcc_binutils_symbol.patch This patch fix makefile.mk to use gcc mapfile under Solaris gcc build environment. python-Python-2.2.2.patch-solaris_gcc_gethostbyname.patch This patch fix gethostbyname declaration. vcl-unx-source-app-stacktrace-asm.patch This patch modify files to use getfpsoli.s instead of C function.
Hi 'taniguchi', this looks like a number of quite useful patches. If you think the patches are ready for integration you might want to make the porting project aware of this issue (if not already done at dev@porting.openoffice.o). Currently you are the owner of the issue and we have to look for the people doing the review and CVS commits... Greetings, Stefan
Hi, Stefan. Thank you for your attention. I'm porting these patches to 680 tree because I think they are not good for 645 tree. But I'm stopping porting because I'm busy with my real work and QA for Japanese version of OOo Solaris binaries is the most I can do. Would you change status of this issue to INVALID? I'll file new issues when I finish porting to 680 tree. Best regards, yasuaki.
Hi Yasuaki, thanks for your efforts so far. I would recommend to let dev@porting know before you start work on the port again. Have fun with real life work Stefan
.