https://wiki.openoffice.org/w/api.php?action=feedcontributions&feedformat=atom&user=KostmoApache OpenOffice Wiki - User contributions [en]2026-10-17T23:02:46ZUser contributionsMediaWiki 1.35.14https://wiki.openoffice.org/w/index.php?title=Art/Resources&diff=152508Art/Resources2009-12-14T01:40:57Z<p>Kostmo: /* Icons */</p>
<hr />
<div>{{Art}} {{DISPLAYTITLE:Official Resources}}<br />
[[Category:Art]]<br />
This page houses official/approved materials that all community members can download and use.<br />
<br />
== Promotional Graphics ==<br />
<br />
* [http://marketing.openoffice.org/art/galleries/marketing/web_buttons/ Web buttons]<br />
* [http://marketing.openoffice.org/art/galleries/marketing/web_banners/ Web banners]<br />
<br />
== Core Design Elements ==<br />
<br />
* [[Art/OOo3 Design|OOo3 Design]]<br />
* [http://marketing.openoffice.org/art/galleries/marketing/design_elements Main Design Elements from OOo2]<br />
* [http://marketing.openoffice.org/art/galleries/marketing/splashscreens Splash Screens for OOo2]<br />
<br />
== Print Materials ==<br />
<br />
=== Business Cards ===<br />
* [http://marketing.openoffice.org/art/galleries/marketing/businesscards Business Cards]<br />
<br />
=== Posters ===<br />
* [http://marketing.openoffice.org/art/galleries/marketing/posters OOo Posters]<br />
<br />
== CD/DVD Labels ==<br />
<br />
* [http://marketing.openoffice.org/art/galleries/cdart/ CD/DVD Labels]<br />
<br />
== Logos ==<br />
<br />
* OpenOffice.org logos [http://marketing.openoffice.org/art/galleries/marketing/logos/ can be found on this page]. Please see the [[Art/Logo/License|Logo License]] for information about usage.<br />
<br />
== Website ==<br />
<br />
* Graphics and templates relating to the OpenOffice.org website can be found at the [[Website/Style_Guide| Website Style Guide]].<br />
<br />
== Icons ==<br />
See [[:Category:Icons]]<br />
<br />
Icons in the source code:<br />
*[http://svn.services.openoffice.org/opengrok/xref/Current%20%28trunk%29/default_images/ default_images]<br />
*[http://svn.services.openoffice.org/opengrok/xref/Current%20%28trunk%29/ooo_custom_images/ ooo_custom_images]<br />
*[http://svn.services.openoffice.org/opengrok/xref/Current%20%28trunk%29/external_images/ external_images]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Art/Resources&diff=152507Art/Resources2009-12-14T01:34:53Z<p>Kostmo: /* Icons */</p>
<hr />
<div>{{Art}} {{DISPLAYTITLE:Official Resources}}<br />
[[Category:Art]]<br />
This page houses official/approved materials that all community members can download and use.<br />
<br />
== Promotional Graphics ==<br />
<br />
* [http://marketing.openoffice.org/art/galleries/marketing/web_buttons/ Web buttons]<br />
* [http://marketing.openoffice.org/art/galleries/marketing/web_banners/ Web banners]<br />
<br />
== Core Design Elements ==<br />
<br />
* [[Art/OOo3 Design|OOo3 Design]]<br />
* [http://marketing.openoffice.org/art/galleries/marketing/design_elements Main Design Elements from OOo2]<br />
* [http://marketing.openoffice.org/art/galleries/marketing/splashscreens Splash Screens for OOo2]<br />
<br />
== Print Materials ==<br />
<br />
=== Business Cards ===<br />
* [http://marketing.openoffice.org/art/galleries/marketing/businesscards Business Cards]<br />
<br />
=== Posters ===<br />
* [http://marketing.openoffice.org/art/galleries/marketing/posters OOo Posters]<br />
<br />
== CD/DVD Labels ==<br />
<br />
* [http://marketing.openoffice.org/art/galleries/cdart/ CD/DVD Labels]<br />
<br />
== Logos ==<br />
<br />
* OpenOffice.org logos [http://marketing.openoffice.org/art/galleries/marketing/logos/ can be found on this page]. Please see the [[Art/Logo/License|Logo License]] for information about usage.<br />
<br />
== Website ==<br />
<br />
* Graphics and templates relating to the OpenOffice.org website can be found at the [[Website/Style_Guide| Website Style Guide]].<br />
<br />
== Icons ==<br />
See [[:Category:Icons]]<br />
<br />
[http://svn.services.openoffice.org/opengrok/xref/Current%20%28trunk%29/ooo_custom_images/ Icons in the source code]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Art/Resources&diff=152506Art/Resources2009-12-14T01:10:27Z<p>Kostmo: Was looking for icons -- shouldn't they be in the Art Project?</p>
<hr />
<div>{{Art}} {{DISPLAYTITLE:Official Resources}}<br />
[[Category:Art]]<br />
This page houses official/approved materials that all community members can download and use.<br />
<br />
== Promotional Graphics ==<br />
<br />
* [http://marketing.openoffice.org/art/galleries/marketing/web_buttons/ Web buttons]<br />
* [http://marketing.openoffice.org/art/galleries/marketing/web_banners/ Web banners]<br />
<br />
== Core Design Elements ==<br />
<br />
* [[Art/OOo3 Design|OOo3 Design]]<br />
* [http://marketing.openoffice.org/art/galleries/marketing/design_elements Main Design Elements from OOo2]<br />
* [http://marketing.openoffice.org/art/galleries/marketing/splashscreens Splash Screens for OOo2]<br />
<br />
== Print Materials ==<br />
<br />
=== Business Cards ===<br />
* [http://marketing.openoffice.org/art/galleries/marketing/businesscards Business Cards]<br />
<br />
=== Posters ===<br />
* [http://marketing.openoffice.org/art/galleries/marketing/posters OOo Posters]<br />
<br />
== CD/DVD Labels ==<br />
<br />
* [http://marketing.openoffice.org/art/galleries/cdart/ CD/DVD Labels]<br />
<br />
== Logos ==<br />
<br />
* OpenOffice.org logos [http://marketing.openoffice.org/art/galleries/marketing/logos/ can be found on this page]. Please see the [[Art/Logo/License|Logo License]] for information about usage.<br />
<br />
== Website ==<br />
<br />
* Graphics and templates relating to the OpenOffice.org website can be found at the [[Website/Style_Guide| Website Style Guide]].<br />
<br />
== Icons ==<br />
See [[:Category:Icons]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11578Ubuntu Build Instructions2006-06-01T08:43:09Z<p>Kostmo: it was a bad hard drive</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Necessary ./configure Flags===<br />
*'''--disable-gtk''' &mdash; This has to be disabled, otherwise <code>make</code> will get hung up on the dbus-glib-1 version 0.60 requirement. The highest version of that package available for Ubuntu is 0.36.2.<br />
<br />
===Failed patches===<br />
[[Talk:Ubuntu_Build_Instructions#Failed_Patches|Some of the patches]] listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
/usr/bin/time --quiet -f %E make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
For the purpose of this tutorial, save the file as <code>make_wrapper.sh</code>. To make it executable, type <code>chmod 744 make_wrapper.sh</code>.<br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ~/ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
<br />
make<br />
#Or if you want an audible alert,<br />
#~/make_wrapper.sh<br />
</pre><br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
*[http://www.go-oo.org OpenOffice.org Hackers Pages]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11130Talk:Ubuntu Build Instructions2006-05-26T10:37:09Z<p>Kostmo: /* Errors after installing ''j2sdk1.4'' along with ''gjc'' */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]])==<br />
===Failed Patches===<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
====Patching HEAD====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
====Patching ooo-build-2-0-2 (02:37, 26 May 2006 (CEST))====<br />
*ubuntu-dictionary.diff<br />
<br />
===Errors compiling ooo-build===<br />
====HEAD====<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====ooo-build-2-0-2 (02:35, 26 May 2006 (CEST))====<br />
<pre><br />
/home/kostmo/ooo-build/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/makedepend: error: makedepend: Failed to read file "hbox.cpp"<br />
dmake: Error code 1, while making '../unxlngi6.pro/misc/s_hbox.dpcc'<br />
dmake: '../unxlngi6.pro/misc/s_hbox.dpcc' removed.<br />
'---* TG_SLO.MK *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hwpfilter/source<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors with ''gcj'' in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors after installing ''j2sdk1.4'' along with ''gjc''====<br />
With j2sdk1.4 installed (requires enabling '''multiverse''' package sources), the above error is eliminated. However, a few hours into the build I got:<br />
<pre><br />
Making: ../../unxlngi6.pro/slb/dapp.lib<br />
echo unxlngi6.pro/slo/dinst.o unxlngi6.pro/slo/dbmp.o | xargs -n1 > ../../unxlngi6.pro/slb/dapp.lib<br />
-------------<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/vcl/unx/gtk/a11y<br />
<br />
ERROR: Error 11 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/vcl/unx/gtk/a11y<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
I had disabled <code>gtk</code> ([http://wiki.services.openoffice.org/wiki/Ubuntu_Build_Instructions#Necessary_..2Fconfigure_Flags see why]) and <code>kde</code>. Apparently [http://lists.ximian.com/pipermail/openoffice/2006-May/001809.html someone else had this problem].<br />
11:09, 26 May 2006 (CEST)<br />
<br />
====dbus-glib-1 library requirement====<br />
<pre><br />
checking for dbus-glib-1 >= 0.60... Package dbus-glib-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `dbus-glib-1.pc' to the PKG_CONFIG_PATH environment variable No package 'dbus-glib-1' foundconfigure: error: Library requirements (dbus-glib-1 >= 0.60) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
<pre><br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
</pre><br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11120Talk:Ubuntu Build Instructions2006-05-26T09:59:14Z<p>Kostmo: /* Errors with ''gjc'' in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST)) */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]])==<br />
===Failed Patches===<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
====Patching HEAD====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
====Patching ooo-build-2-0-2 (02:37, 26 May 2006 (CEST))====<br />
*ubuntu-dictionary.diff<br />
<br />
===Errors compiling ooo-build===<br />
====HEAD====<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====ooo-build-2-0-2 (02:35, 26 May 2006 (CEST))====<br />
<pre><br />
/home/kostmo/ooo-build/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/makedepend: error: makedepend: Failed to read file "hbox.cpp"<br />
dmake: Error code 1, while making '../unxlngi6.pro/misc/s_hbox.dpcc'<br />
dmake: '../unxlngi6.pro/misc/s_hbox.dpcc' removed.<br />
'---* TG_SLO.MK *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hwpfilter/source<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors with ''gcj'' in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors after installing ''j2sdk1.4'' along with ''gjc''====<br />
With j2sdk1.4 installed (requires enabling '''multiverse''' package sources), the above error is eliminated. However, a few hours into the build I got:<br />
<pre><br />
Making: ../../unxlngi6.pro/slb/dapp.lib<br />
echo unxlngi6.pro/slo/dinst.o unxlngi6.pro/slo/dbmp.o | xargs -n1 > ../../unxlngi6.pro/slb/dapp.lib<br />
-------------<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/vcl/unx/gtk/a11y<br />
<br />
ERROR: Error 11 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/vcl/unx/gtk/a11y<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
I had disabled both <code>kde</code> and <code>gtk</code>. Apparently [http://lists.ximian.com/pipermail/openoffice/2006-May/001809.html someone else had this problem].<br />
11:09, 26 May 2006 (CEST)<br />
<br />
====dbus-glib-1 library requirement====<br />
<pre><br />
checking for dbus-glib-1 >= 0.60... Package dbus-glib-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `dbus-glib-1.pc' to the PKG_CONFIG_PATH environment variable No package 'dbus-glib-1' foundconfigure: error: Library requirements (dbus-glib-1 >= 0.60) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
<pre><br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
</pre><br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11118Talk:Ubuntu Build Instructions2006-05-26T09:45:38Z<p>Kostmo: /* Errors after installing ''j2sdk1.4'' along with ''gjc'' */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]])==<br />
===Failed Patches===<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
====Patching HEAD====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
====Patching ooo-build-2-0-2 (02:37, 26 May 2006 (CEST))====<br />
*ubuntu-dictionary.diff<br />
<br />
===Errors compiling ooo-build===<br />
====HEAD====<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====ooo-build-2-0-2 (02:35, 26 May 2006 (CEST))====<br />
<pre><br />
/home/kostmo/ooo-build/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/makedepend: error: makedepend: Failed to read file "hbox.cpp"<br />
dmake: Error code 1, while making '../unxlngi6.pro/misc/s_hbox.dpcc'<br />
dmake: '../unxlngi6.pro/misc/s_hbox.dpcc' removed.<br />
'---* TG_SLO.MK *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hwpfilter/source<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors with ''gjc'' in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors after installing ''j2sdk1.4'' along with ''gjc''====<br />
With j2sdk1.4 installed (requires enabling '''multiverse''' package sources), the above error is eliminated. However, a few hours into the build I got:<br />
<pre><br />
Making: ../../unxlngi6.pro/slb/dapp.lib<br />
echo unxlngi6.pro/slo/dinst.o unxlngi6.pro/slo/dbmp.o | xargs -n1 > ../../unxlngi6.pro/slb/dapp.lib<br />
-------------<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/vcl/unx/gtk/a11y<br />
<br />
ERROR: Error 11 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/vcl/unx/gtk/a11y<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
I had disabled both <code>kde</code> and <code>gtk</code>. Apparently [http://lists.ximian.com/pipermail/openoffice/2006-May/001809.html someone else had this problem].<br />
11:09, 26 May 2006 (CEST)<br />
<br />
====dbus-glib-1 library requirement====<br />
<pre><br />
checking for dbus-glib-1 >= 0.60... Package dbus-glib-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `dbus-glib-1.pc' to the PKG_CONFIG_PATH environment variable No package 'dbus-glib-1' foundconfigure: error: Library requirements (dbus-glib-1 >= 0.60) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
<pre><br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
</pre><br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11111Ubuntu Build Instructions2006-05-26T09:15:10Z<p>Kostmo: /* Caveats */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Necessary ./configure Flags===<br />
*'''--disable-gtk''' &mdash; This has to be disabled, otherwise <code>make</code> will get hung up on the dbus-glib-1 version 0.60 requirement. The highest version of that package available for Ubuntu is 0.36.2.<br />
<br />
===Failed patches===<br />
[[Talk:Ubuntu_Build_Instructions#Failed_Patches|Some of the patches]] listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
/usr/bin/time --quiet -f %E make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
For the purpose of this tutorial, save the file as <code>make_wrapper.sh</code>. To make it executable, type <code>chmod 744 make_wrapper.sh</code>.<br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ~/ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
<br />
make<br />
#Or if you want an audible alert,<br />
#~/make_wrapper.sh<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail (or maybe it only does that if you have a bad hard drive?).<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
*[http://www.go-oo.org OpenOffice.org Hackers Pages]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11110Ubuntu Build Instructions2006-05-26T09:13:08Z<p>Kostmo: /* Necessary ./configure Flags */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Necessary ./configure Flags===<br />
*'''--disable-gtk''' &mdash; This has to be disabled, otherwise <code>make</code> will get hung up on the dbus-glib-1 version 0.60 requirement. The highest version of that package available for Ubuntu is 0.36.2.<br />
<br />
===Failed patches===<br />
[[Talk:Ubuntu_Build_Instructions#Failed_Patches|Some of the patches]] listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
/usr/bin/time --quiet -f %E make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
For the purpose of this tutorial, save the file as <code>make_wrapper.sh</code>. To make it executable, type <code>chmod 744 make_wrapper.sh</code>.<br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ~/ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
<br />
make<br />
#Or if you want an audible alert,<br />
#~/make_wrapper.sh<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
*[http://www.go-oo.org OpenOffice.org Hackers Pages]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11108Talk:Ubuntu Build Instructions2006-05-26T09:10:25Z<p>Kostmo: /* Errors after installing ''j2sdk1.4'' along with ''gjc'' */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]])==<br />
===Failed Patches===<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
====Patching HEAD====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
====Patching ooo-build-2-0-2 (02:37, 26 May 2006 (CEST))====<br />
*ubuntu-dictionary.diff<br />
<br />
===Errors compiling ooo-build===<br />
====HEAD====<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====ooo-build-2-0-2 (02:35, 26 May 2006 (CEST))====<br />
<pre><br />
/home/kostmo/ooo-build/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/makedepend: error: makedepend: Failed to read file "hbox.cpp"<br />
dmake: Error code 1, while making '../unxlngi6.pro/misc/s_hbox.dpcc'<br />
dmake: '../unxlngi6.pro/misc/s_hbox.dpcc' removed.<br />
'---* TG_SLO.MK *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hwpfilter/source<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors with ''gjc'' in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors after installing ''j2sdk1.4'' along with ''gjc''====<br />
With j2sdk1.4 installed (requires enabling '''multiverse''' package sources), the above error is eliminated. However, a few hours into the build I got:<br />
<pre><br />
Making: ../../unxlngi6.pro/slb/dapp.lib<br />
echo unxlngi6.pro/slo/dinst.o unxlngi6.pro/slo/dbmp.o | xargs -n1 > ../../unxlngi6.pro/slb/dapp.lib<br />
-------------<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/vcl/unx/gtk/a11y<br />
<br />
ERROR: Error 11 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/vcl/unx/gtk/a11y<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
11:09, 26 May 2006 (CEST)<br />
<br />
====dbus-glib-1 library requirement====<br />
<pre><br />
checking for dbus-glib-1 >= 0.60... Package dbus-glib-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `dbus-glib-1.pc' to the PKG_CONFIG_PATH environment variable No package 'dbus-glib-1' foundconfigure: error: Library requirements (dbus-glib-1 >= 0.60) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
<pre><br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
</pre><br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11107Talk:Ubuntu Build Instructions2006-05-26T09:09:30Z<p>Kostmo: /* Errors after installing ''j2sdk1.4'' along with ''gjc'' */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]])==<br />
===Failed Patches===<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
====Patching HEAD====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
====Patching ooo-build-2-0-2 (02:37, 26 May 2006 (CEST))====<br />
*ubuntu-dictionary.diff<br />
<br />
===Errors compiling ooo-build===<br />
====HEAD====<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====ooo-build-2-0-2 (02:35, 26 May 2006 (CEST))====<br />
<pre><br />
/home/kostmo/ooo-build/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/makedepend: error: makedepend: Failed to read file "hbox.cpp"<br />
dmake: Error code 1, while making '../unxlngi6.pro/misc/s_hbox.dpcc'<br />
dmake: '../unxlngi6.pro/misc/s_hbox.dpcc' removed.<br />
'---* TG_SLO.MK *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hwpfilter/source<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors with ''gjc'' in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors after installing ''j2sdk1.4'' along with ''gjc''====<br />
With j2sdk1.4 installed (requires enabling '''multiverse''' package sources), the above error is elminated. However, a few hours into the build I got:<br />
<pre><br />
Making: ../../unxlngi6.pro/slb/dapp.lib<br />
echo unxlngi6.pro/slo/dinst.o unxlngi6.pro/slo/dbmp.o | xargs -n1 > ../../unxlngi6.pro/slb/dapp.lib<br />
-------------<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/vcl/unx/gtk/a11y<br />
<br />
ERROR: Error 11 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/vcl/unx/gtk/a11y<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
11:09, 26 May 2006 (CEST)<br />
<br />
====dbus-glib-1 library requirement====<br />
<pre><br />
checking for dbus-glib-1 >= 0.60... Package dbus-glib-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `dbus-glib-1.pc' to the PKG_CONFIG_PATH environment variable No package 'dbus-glib-1' foundconfigure: error: Library requirements (dbus-glib-1 >= 0.60) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
<pre><br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
</pre><br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11105Talk:Ubuntu Build Instructions2006-05-26T09:03:36Z<p>Kostmo: /* Errors after installing ''j2sdk1.4'' along with ''gjc'' */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]])==<br />
===Failed Patches===<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
====Patching HEAD====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
====Patching ooo-build-2-0-2 (02:37, 26 May 2006 (CEST))====<br />
*ubuntu-dictionary.diff<br />
<br />
===Errors compiling ooo-build===<br />
====HEAD====<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====ooo-build-2-0-2 (02:35, 26 May 2006 (CEST))====<br />
<pre><br />
/home/kostmo/ooo-build/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/makedepend: error: makedepend: Failed to read file "hbox.cpp"<br />
dmake: Error code 1, while making '../unxlngi6.pro/misc/s_hbox.dpcc'<br />
dmake: '../unxlngi6.pro/misc/s_hbox.dpcc' removed.<br />
'---* TG_SLO.MK *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hwpfilter/source<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors with ''gjc'' in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors after installing ''j2sdk1.4'' along with ''gjc''====<br />
With j2sdk1.4 installed (requires enabling '''multiverse''' package sources), the above error is elminated. However, a few hours into the build I got:<br />
<pre><br />
Making: ../../unxlngi6.pro/slb/dapp.lib<br />
echo unxlngi6.pro/slo/dinst.o unxlngi6.pro/slo/dbmp.o | xargs -n1 > ../../unxlngi6.pro/slb/dapp.lib<br />
-------------<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/vcl/unx/gtk/a11y<br />
<br />
ERROR: Error 11 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/vcl/unx/gtk/a11y<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====dbus-glib-1 library requirement====<br />
<pre><br />
checking for dbus-glib-1 >= 0.60... Package dbus-glib-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `dbus-glib-1.pc' to the PKG_CONFIG_PATH environment variable No package 'dbus-glib-1' foundconfigure: error: Library requirements (dbus-glib-1 >= 0.60) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
<pre><br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
</pre><br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11090Talk:Ubuntu Build Instructions2006-05-26T08:13:56Z<p>Kostmo: /* Errors caused by gjc in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST)) */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]])==<br />
===Failed Patches===<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
====Patching HEAD====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
====Patching ooo-build-2-0-2 (02:37, 26 May 2006 (CEST))====<br />
*ubuntu-dictionary.diff<br />
<br />
===Errors compiling ooo-build===<br />
====HEAD====<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====ooo-build-2-0-2 (02:35, 26 May 2006 (CEST))====<br />
<pre><br />
/home/kostmo/ooo-build/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/makedepend: error: makedepend: Failed to read file "hbox.cpp"<br />
dmake: Error code 1, while making '../unxlngi6.pro/misc/s_hbox.dpcc'<br />
dmake: '../unxlngi6.pro/misc/s_hbox.dpcc' removed.<br />
'---* TG_SLO.MK *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hwpfilter/source<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors with ''gjc'' in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors after installing ''j2sdk1.4'' along with ''gjc''====<br />
With j2sdk1.4 installed (requires enabling '''multiverse''' package sources), the above error is elminated.<br />
<br />
====dbus-glib-1 library requirement====<br />
<pre><br />
checking for dbus-glib-1 >= 0.60... Package dbus-glib-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `dbus-glib-1.pc' to the PKG_CONFIG_PATH environment variable No package 'dbus-glib-1' foundconfigure: error: Library requirements (dbus-glib-1 >= 0.60) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
<pre><br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
</pre><br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ooo-build&diff=11083Ooo-build2006-05-26T05:51:16Z<p>Kostmo: /* compile fragility */</p>
<hr />
<div>This collection of patches, artwork and build infrastructure exists solely as a reflection of the many problems encouraging reasonably responsive change up-stream. The process of change is painful for any organisation, the larger the more painful. However - the size of the problem is no excuse to not try; hence the evenutal aim is to remove the need for ooo-build by incrementally fixing the various problems.<br />
<br />
== About ooo-build ==<br />
<br />
ooo-build arose from acute frustration with the bad-old days of OOo process before the [[CWS|Child Workspace]] concept was introduced, it is<br />
also fueled by a non-performant [[Infrastructure_Problems#CVS|CVS server]].<br />
<br />
* [[ooo-build/bin]] - A description of the tools in bin/<br />
<br />
== sample simple fixes ==<br />
<br />
=== Win32 / configure auto-detection ===<br />
<br />
We have a nice perl script 'oowintool' that does a rather better job of auto-detecting various system tools than up-stream, we should integrate it there - it makes the common case much easier. cf. the last point though.<br />
<br />
=== branding / artwork / splash bits ===<br />
<br />
Many of the ooo-build patches are simply branding changes for other distros. Getting that up-stream plus a combination of selectable 'experimental' features would prolly remove the usefulness of ooo-build substantially<br />
for these people. Altenatively perhaps good docs and a <code>--with-splash=/tmp/foo.png --with-logo=/tmp/baa.bmp</code> might work nicely.<br />
<br />
=== faster 1st time (packagers/developers) build ===<br />
<br />
Dependency generation takes a huge chunk of CPU time - simply detecting a pristine build & exporting 'nodep=1' trivially saves a chunk of time - should get that up-stream.<br />
<br />
=== easier developer experience ===<br />
<br />
Trivial, built-in, automated use of the system malloc allocator checker (via linkoo &amp; source ooenv), also - by default disabling the (incredibly annoying) 'recover from crash' dialog stuff via a similar trivial environment variable patch: i#54275.<br />
<br />
== remaining unsolved issue summary ==<br />
<br />
A helpful summary of these is provided here in no particular order along with suggestions for improvement.<br />
Many of these are mercifully easy to fix, and should be fixed soon.<br />
<br />
=== source handling ===<br />
<br />
==== src packaging ====<br />
<br />
We have habitually split the source into several pieces to aid downloading. The process of achieving this is codified in a<br />
simple shell-script [[http://go-oo.org/ooo-build/bin/src-pack here]]. It is of course necessary to have source archives that include the CVS directories & information, (or perhaps split that out into another package - but yet make it available) - such that developers can easily 'cvs diff -u' to extract their changes, and of course tinderbox slaves can base off these archives.<br />
<br />
==== src download ====<br />
<br />
ooo-build has a post-configure 'download' mechanism, whereby the relevant source archives will be automatically downloaded to your system having configured it, in response to your various options.<br />
<br />
=== cvs slowness ===<br />
<br />
It can take multiple hours to tag (once) the full up-stream CVS; this is not conducive to some of the more funky<br />
'nested workspace' ideas based on the [[CWS]] tooling becoming a reality. Adding large modules to a cws currently<br />
takes way too long. Interestingly, it's can be quicker to do a $ cvs diff, create a new cws and apply the patch<br />
than re-sync a cws. It also helps to have the diff in hand in case the cws tools fail mid-flow, since that has been known to loose data.<br />
A 'diff -u' by contrast, or an anonymous diff from cvs - combined with ooo-build's intelligent patch application<br />
process often results in an extremely fast development cycle unincumbered by <b>low</b> performance [[Infrastructure_Problems#CVS|CVS server]].<br />
<br />
=== compile fragility ===<br />
<br />
To use up-stream OO.o it is not possible to use HEAD, due to multiple concurrent (slow) incomplete merges constantly in progress, instead one must use a milestone release. Unfortunately milestone releases build on a small number of tested setups - but these typically do not include out-of-the-box, stock Linux distributions<br />
such as OpenSUSE, Fedora, Debian etc. Thus from day-1 it is necessary to patch a milestone to get it to build<br />
at all. Issues such as different gcc versions, different platform libraries etc. tend to cause this.<br />
However - there is no central place where such patches can be collected to avoid constant duplication of effort,<br />
apart from ooo-build.<br />
<br />
It is hoped a [[Tinderbox Setup | tinderbox]] server with many disparate slaves building the CWS in the 'Ready for QA' state might<br />
help fix this problem in future.<br />
<br />
=== interlocking changes ===<br />
<br />
While a cws is waiting to be integrated / going through QA - it is entirely possible that another feature<br />
requires the functionality it provides; furthermore there is no easy way to include multiple features that we<br />
judge to be ready, yet would not pass up-stream QA (on multiple platforms etc.) into our builds. Thus ooo-build<br />
becomes a place to test multiple new features concurrently. It is hoped that the new <i>experimental</i> CWS<br />
regimen may help fix this problem & accelerate up-streaming of patches.<br />
<br />
=== non-responsiveness / lack of leadership ===<br />
<br />
Many ooo-build patches are ready for up-streaming but there is no / little response from up-stream. Worse there is the perception that taking leadership and actually doing something about merging fixes would be firmly opposed. Finally - even when maintainers are active, responsive & friendly - there is no agreed mechanism for blanket<br />
approving fixes - or sub-types of trivial fixes, which thus tend to fester in IssueZilla.<br />
<br />
At the time of writing ooo-build's patches are available here: http://go-oo.org/ooo-build/patches/src680/apply.<br />
<br />
FIXME - add some humerous details here / bug links etc.<br />
<br />
=== symbol font ===<br />
<br />
ooo-build contains a substantially improved OpenSymbol font: opens___.ttf improved mostly but cut/pasting existing glyphs to new positions to match the mapping table in vcl. This results in a massively improved PPT/Word bullet experience with little effort. It is not acceptable up-stream for reasons unexplained.<br />
<br />
=== font substitution ===<br />
<br />
Many vendors ship AGFA's propriatory metric-compatible fonts with OO.o - it is thus necessary to run several seds on the VCL.xcu [ further bloating this already gigantic messy beast ]. We also remove some of the more foolish &amp; enthusiastic font-usage of eg. the metrically-extremely-strange bitstream font eg. <code>bin/font-munge.pl</code><br />
<br />
s/(Bitstream Vera Sans;.*)Albany;/Albany;$1/;<br />
# add AMT fonts<br />
s/Albany;/Albany AMT;Albany;/g;<br />
s/albany;/albanyamt;albany;/g;<br />
<br />
=== parallel build support ===<br />
<br />
There are a chunk of ice-cream / massively parallel fixes in ooo-build, it's not clear who owns reviewing / accepting these up-stream.<br />
<br />
=== no 'UI' team ===<br />
<br />
The up-stream UI team have come up with master-pieces of UI design such as the Yes/No dialog on<br />
<br />
"Would you like to not continue saving in the original OpenOffice.org 2.0 format or perhaps switch to another format"<br />
<br />
that takes 10 seconds to parse each time ( presumably since it's a recent feature - with a specification too ).<br />
<br />
The rest of us mere-mortals know that the OO.o is <b>shockingly</b> broken - and hence are eager to fix it<br />
without being blocked & frustrated for weeks by those responsible for the current mess.<br />
<br />
A number of the changes / patches in apply/ are blocked on 'user experience' feedback.<br />
<br />
=== different defaults ===<br />
<br />
It is self evident to ooo-build users that a slew of dialogs on 1st run is a painful mess; eg. if there are settings to migrate, don't shout about it - do it silently. Furthermore - the registration dialog looks tacky,<br />
we disable both. We also alter a number of other defaults. cf. the last point - I'm optimistic that these will<br />
~never get up-stream agreement.<br />
<br />
=== bleeding-edgeness ===<br />
<br />
There is a 'cool factor' to building the very latest things yourself; and helping solve problems with them.<br />
It's nice to be able to see your changes have an effect &amp; help others rapidly, eg. a fix being immediately<br />
useful to other people. Of course - you can have too much of a good thing here but ...<br />
<br />
=== Philosophical differences ===<br />
<br />
==== compatibility ====<br />
<br />
Up-stream believe that the most important data set to be compatible with is existing StarOffice / OO.o users.<br />
ooo-build users believe that nearly all the world's data is stored in Microsoft Office format - hence we<br />
sacrifice legacy support for better interop.<br />
This is of course a continuum, up-stream are at the luney extreme of pushing back-compatibility regardless<br />
of it's impact on interoperability, even in cases deliberately excluding useful interoperability improvements<br />
on that basis. ooo-build appreciates backwards comaptibility, but is in favour of viewing core differences<br />
that are non-interoperable as bugs not features.<br />
<br />
==== process complexity ====<br />
<br />
ooo-build users believe in programmer lead development, with strong peer review and user QA.<br />
up-stream believe in process based development, with teams, consensus building, specification writing, test-instead-of-detailed-code-review, and all these 'Professional' pasttimes.<br />
ooo-build users believe the OO.o we have today is broadly a product of these processes. Up-stream users<br />
believe the previous sentence is a compliment.<br />
<br />
==== cross-platform ====<br />
<br />
ooo-build enables patch sub-setting, thus we include patches for features (eg. Mono integration) that are<br />
most likely not well separated, and will break the Win32 build. Of course, for ooo-build these are not<br />
enabled on Win32 thus causing no problem. This is an impediment to getting work up-stream. Hopefully<br />
the 'experimental' process may help encourage good behavior here.<br />
<br />
=== FIXME ===<br />
<br />
Lots more to be said here ...<br />
<br />
== Conclusion ==<br />
<br />
If you read all that don't get depressed - these issues can all be fixed - many of them almost painlessly. We hope to shrink this page quickly.<br />
<br />
[[Category: Development]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Category:Distribution-Specific_Build_Instructions&diff=11082Category:Distribution-Specific Build Instructions2006-05-26T05:40:07Z<p>Kostmo: </p>
<hr />
<div>Yes, [[ooo-build]] has distribution-specific behavior. Most of the differences lie in package naming (e.g. '''''xxx''-devel''' on Fedora/SuSE vs '''lib''xxx''-dev''' on Debian/Ubuntu) and availability.<br />
<br />
You may be safest going with SuSE, since that's where most of the development seems to be happening, but everyone has their favorite distro.<br />
<br />
[[Category: Development]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Category:Distribution-Specific_Build_Instructions&diff=11081Category:Distribution-Specific Build Instructions2006-05-26T05:37:59Z<p>Kostmo: </p>
<hr />
<div>Yes, [[ooo-build]] has distribution-specific behavior. Most of the differences lie in package naming and availability (e.g. xxx-devel on Fedora/SuSE vs libxxx-dev on Debian/Ubuntu).<br />
<br />
You may be safest going with SuSE, since that's where most of the development seems to be happening, but everyone has their favorite distro.<br />
<br />
[[Category: Development]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11080Ubuntu Build Instructions2006-05-26T05:29:49Z<p>Kostmo: /* See also */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Necessary ./configure Flags===<br />
*'''--disable-gtk''' &mdash; This has to be disabled, otherwise <code>make</code> will get hung up on the dbus-glib-1 version 0.60 requirement. The highest version of that package available for Ubuntu is 0.32.<br />
<br />
===Failed patches===<br />
[[Talk:Ubuntu_Build_Instructions#Failed_Patches|Some of the patches]] listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
/usr/bin/time --quiet -f %E make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
For the purpose of this tutorial, save the file as <code>make_wrapper.sh</code>. To make it executable, type <code>chmod 744 make_wrapper.sh</code>.<br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ~/ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
<br />
make<br />
#Or if you want an audible alert,<br />
#~/make_wrapper.sh<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
*[http://www.go-oo.org OpenOffice.org Hackers Pages]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11079Talk:Ubuntu Build Instructions2006-05-26T04:53:48Z<p>Kostmo: /* Errors caused by running ''ubdatedb'' */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]])==<br />
===Failed Patches===<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
====Patching HEAD====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
====Patching ooo-build-2-0-2 (02:37, 26 May 2006 (CEST))====<br />
*ubuntu-dictionary.diff<br />
<br />
===Errors compiling ooo-build===<br />
====HEAD====<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====ooo-build-2-0-2 (02:35, 26 May 2006 (CEST))====<br />
<pre><br />
/home/kostmo/ooo-build/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/makedepend: error: makedepend: Failed to read file "hbox.cpp"<br />
dmake: Error code 1, while making '../unxlngi6.pro/misc/s_hbox.dpcc'<br />
dmake: '../unxlngi6.pro/misc/s_hbox.dpcc' removed.<br />
'---* TG_SLO.MK *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hwpfilter/source<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by gjc in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====dbus-glib-1 library requirement====<br />
<pre><br />
checking for dbus-glib-1 >= 0.60... Package dbus-glib-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `dbus-glib-1.pc' to the PKG_CONFIG_PATH environment variable No package 'dbus-glib-1' foundconfigure: error: Library requirements (dbus-glib-1 >= 0.60) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
<pre><br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
</pre><br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11078Ubuntu Build Instructions2006-05-26T04:46:32Z<p>Kostmo: /* Failed patches */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Necessary ./configure Flags===<br />
*'''--disable-gtk''' &mdash; This has to be disabled, otherwise <code>make</code> will get hung up on the dbus-glib-1 version 0.60 requirement. The highest version of that package available for Ubuntu is 0.32.<br />
<br />
===Failed patches===<br />
[[Talk:Ubuntu_Build_Instructions#Failed_Patches|Some of the patches]] listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
/usr/bin/time --quiet -f %E make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
For the purpose of this tutorial, save the file as <code>make_wrapper.sh</code>. To make it executable, type <code>chmod 744 make_wrapper.sh</code>.<br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ~/ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
<br />
make<br />
#Or if you want an audible alert,<br />
#~/make_wrapper.sh<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11077Ubuntu Build Instructions2006-05-26T03:32:23Z<p>Kostmo: /* Tips */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
[[Talk:Ubuntu_Build_Instructions#Failed_Patches|Some of the patches]] listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
/usr/bin/time --quiet -f %E make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
For the purpose of this tutorial, save the file as <code>make_wrapper.sh</code>. To make it executable, type <code>chmod 744 make_wrapper.sh</code>.<br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ~/ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
<br />
make<br />
#Or if you want an audible alert,<br />
#~/make_wrapper.sh<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11076Talk:Ubuntu Build Instructions2006-05-26T02:01:50Z<p>Kostmo: /* Build Problems (Kostmo 10:24, 24 May 2006 (CEST)) */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]])==<br />
===Failed Patches===<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
====Patching HEAD====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
====Patching ooo-build-2-0-2 (02:37, 26 May 2006 (CEST))====<br />
*ubuntu-dictionary.diff<br />
<br />
===Errors compiling ooo-build===<br />
====HEAD====<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====ooo-build-2-0-2 (02:35, 26 May 2006 (CEST))====<br />
<pre><br />
/home/kostmo/ooo-build/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/makedepend: error: makedepend: Failed to read file "hbox.cpp"<br />
dmake: Error code 1, while making '../unxlngi6.pro/misc/s_hbox.dpcc'<br />
dmake: '../unxlngi6.pro/misc/s_hbox.dpcc' removed.<br />
'---* TG_SLO.MK *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hwpfilter/source<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by gjc in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11075Ubuntu Build Instructions2006-05-26T02:00:56Z<p>Kostmo: /* Failed patches */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
[[Talk:Ubuntu_Build_Instructions#Failed_Patches|Some of the patches]] listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
For the purpose of this tutorial, save the file as <code>make_wrapper.sh</code>. To make it executable, type <code>chmod 744 make_wrapper.sh</code>.<br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ~/ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
<br />
make<br />
#Or if you want an audible alert,<br />
#~/make_wrapper.sh<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11074Ubuntu Build Instructions2006-05-26T01:36:10Z<p>Kostmo: /* Development Environment Preparation Script */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
For the purpose of this tutorial, save the file as <code>make_wrapper.sh</code>. To make it executable, type <code>chmod 744 make_wrapper.sh</code>.<br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ~/ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
<br />
make<br />
#Or if you want an audible alert,<br />
#~/make_wrapper.sh<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11073Ubuntu Build Instructions2006-05-26T01:23:31Z<p>Kostmo: /* Development Environment Preparation Script */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
For the purpose of this tutorial, save the file as <code>make_wrapper.sh</code>. To make it executable, type <code>chmod 744 make_wrapper.sh</code>.<br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ~/ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
<br />
make<br />
#Or if you want an audio alert,<br />
#~/make_wrapper.sh<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11072Ubuntu Build Instructions2006-05-26T01:22:49Z<p>Kostmo: /* Development Environment Preparation Script */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
For the purpose of this tutorial, save the file as <code>make_wrapper.sh</code>. To make it executable, type <code>chmod 744 make_wrapper.sh</code>.<br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ~/ooo-build<br />
./autogen.sh --with-distro=Ubuntu<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
<br />
make<br />
#Or if you want an audio alert,<br />
#~/make_wrapper.sh<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11071Talk:Ubuntu Build Instructions2006-05-26T01:16:26Z<p>Kostmo: /* ooo-build-2-0-2 (02:37, 26 May 2006 (CEST)) */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]] 10:24, 24 May 2006 (CEST))==<br />
===Failed Patches===<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
====Patching HEAD====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
====Patching ooo-build-2-0-2 (02:37, 26 May 2006 (CEST))====<br />
*ubuntu-dictionary.diff<br />
<br />
===Errors compiling ooo-build===<br />
====HEAD====<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====ooo-build-2-0-2 (02:35, 26 May 2006 (CEST))====<br />
<pre><br />
/home/kostmo/ooo-build/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/makedepend: error: makedepend: Failed to read file "hbox.cpp"<br />
dmake: Error code 1, while making '../unxlngi6.pro/misc/s_hbox.dpcc'<br />
dmake: '../unxlngi6.pro/misc/s_hbox.dpcc' removed.<br />
'---* TG_SLO.MK *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hwpfilter/source<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by gjc in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11070Talk:Ubuntu Build Instructions2006-05-26T01:16:08Z<p>Kostmo: /* HEAD */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]] 10:24, 24 May 2006 (CEST))==<br />
===Failed Patches===<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
====Patching HEAD====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
====ooo-build-2-0-2 (02:37, 26 May 2006 (CEST))====<br />
*ubuntu-dictionary.diff<br />
<br />
===Errors compiling ooo-build===<br />
====HEAD====<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====ooo-build-2-0-2 (02:35, 26 May 2006 (CEST))====<br />
<pre><br />
/home/kostmo/ooo-build/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/makedepend: error: makedepend: Failed to read file "hbox.cpp"<br />
dmake: Error code 1, while making '../unxlngi6.pro/misc/s_hbox.dpcc'<br />
dmake: '../unxlngi6.pro/misc/s_hbox.dpcc' removed.<br />
'---* TG_SLO.MK *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hwpfilter/source<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by gjc in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11069Ubuntu Build Instructions2006-05-26T01:15:17Z<p>Kostmo: /* Development Environment Preparation Script */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
For the purpose of this tutorial, save the file as <code>make_wrapper.sh</code>. To make it executable, type <code>chmod 744 make_wrapper.sh</code>.<br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant kdebase-dev<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ~/ooo-build<br />
./autogen.sh --with-distro=Ubuntu<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
<br />
make<br />
#Or if you want an audio alert,<br />
#~/make_wrapper.sh<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11068Ubuntu Build Instructions2006-05-26T01:13:52Z<p>Kostmo: /* Development Environment Preparation Script */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
For the purpose of this tutorial, save the file as <code>make_wrapper.sh</code>. To make it executable, type <code>chmod 744 make_wrapper.sh</code>.<br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant kdebase-dev<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ooo-build<br />
./autogen.sh --with-distro=Ubuntu<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
<br />
make<br />
#Or if you want an audio alert,<br />
#../make_wrapper.sh<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11067Ubuntu Build Instructions2006-05-26T01:05:28Z<p>Kostmo: /* Tips */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
For the purpose of this tutorial, save the file as <code>make_wrapper.sh</code>. To make it executable, type <code>chmod 744 make_wrapper.sh</code>.<br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant kdebase-dev<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ooo-build<br />
./autogen.sh --with-distro=Ubuntu<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
make<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Building_with_ooobuild&diff=11066Building with ooobuild2006-05-26T00:57:20Z<p>Kostmo: </p>
<hr />
<div>== Vanilla Up-stream builds ==<br />
<br />
See the [http://tools.openoffice.org#Build tools] project for build guides for various platforms.<br />
<br />
Also for OS/X see [[MacOSXBuildInstructions]]<br />
<br />
For GNU/Linux Sparc, with gcc4.1 & gcj, see [[GNULinuxSparcPorting]]<br />
<br />
== ooo-build builds ==<br />
<br />
<center><br />
'''If you are looking for additional building tips for Windows check [[Windows |this]] page first.'''<br />
</center><br />
----<br />
<br><br />
<br />
=== configure ===<br />
<br />
<p><br />
The build process is pretty complicated; you have a choice<br />
of commands now; although running both won't actually hurt:<br />
</p><br />
./autogen.sh # only for the CVS version<br />
./configure # the packaged version<br />
<br />
<p><br />
This will guess which branch snapshot you want to build; if<br />
you have other ideas use the --with-tag option; eg.<br />
<code>--with-tag=src680-m65</code> for a legacy branch.<br />
</p><br />
<p><br />
If for some reason you have a 31337 multi-threaded computer,<br />
with great slabs of RAM; you'll want to use --with-num-cpus=8<br />
etc. NB. it's not clever to force the build to swap like a<br />
demented pawnbroker by using an artificially high number; C++<br />
compilation is seriously memory hungry.<br />
</p><br />
<p><br />
In particular, building SRC680 requires a recent jdk &amp; a<br />
version of apache-ant. If you use a Novell system, just do:<br />
<code>sudo rug in apache-ant</code>, alternatively download<br />
a package from [http://www.rpmfind.net/linux/rpm2html/search.php?query=apache-ant&submit=Search+..." rpmfind.net] or failing that see [http://ant.apache.org/bindownload.cgi Ant download]<br />
&amp; set the ANT environment variable<br />
appropriately before configuring.<br />
</p><br />
<h4>Known ./configure parameters</h4><br />
<ul><br />
<li><h5><code>--with-system-<package name></code></h5><br />
<p>where &lt;package name> is replaced by the package to use. I don't<br />
have a particularly good understanding of its full effects beyond<br />
the fact that it (probably) doesn't then build its own copy of the<br />
package.</p><br />
<p><b>Examples:</b><br><br />
<code>--with-system-python</code><br><br />
<code>--with-system-mozilla</code><br><br />
<code>--with-system-gcc</code><br><br />
<code>--with-system-neon</code><br><br />
<code>--with-system-curl</code><br><br />
</p><br />
</li><br />
<li><h5><code>--without-system-<package name></code></h5><br />
<p><b>Examples:</b><br><br />
<code>--without-system-mozilla</code><br />
</p><br />
</li><br />
<li><h5><code>--with-<package or tag>[=value]</code></h5><br />
<p><b>Examples:</b><br><br />
<code>--with-lang=en-US</code><br><br />
<code>--with-build-version="Build 2.0.1.3"</code><br><br />
<code>--with-distro=Gentoo</code><br><br />
</p><br />
</li><br />
<li><h5><code>--without-<package or tag></code></h5><br />
<p><b>Examples:</b><br><br />
<code>--without-myspell-dicts</code><br><br />
<code>--without-java</code><br><br />
<code>--without-nas</code><br><br />
</p><br />
</li><br />
<li><h5><code>--enable-<package name></code></h5><br />
<p><b>Examples:</b><br><br />
<code>--enable-openldap</code><br><br />
</p><br />
</li><br />
<li><h5><code>--disable-<package name></code></h5><br />
<p><b>Examples:</b><br><br />
<code>--disable-openldap</code><br><br />
<code>--disable-qadevoo</code><br><br />
<code>--disable-mozilla</code><br><br />
<code>--disable-access</code><br><br />
<code>--disable-evolution2</code><br><br />
</p><br />
</li><br />
<li><h5><code>--mandir=<dir></code></h5></li><br />
</ul><br />
<br />
=== Requirements ===<br />
*A recent version of automake, such as the 1.9 series.<br />
*If you don't have a working Java VM (i.e. any runtime), you should pass <code>--with-java=no</code> to either <code>autogen.sh</code> or <code>configure</code>.<br />
*You need the Archive/Zip module for Perl (perl-Archive-Zip on RPM-based distributions, libarchive-zip-perl on dpkg-based distributions). Alternatively, see instructions[http://ooo.ximian.com/cpan.html] for obtaining Perl modules through CPAN.<br />
*You need the development package for Python (this would be python-devel on RPM-based distributions).<br />
*You need curl and curl-devel.<br />
*You need odbc_config to be present. On SUSE systems, this is in the unixODBC-devel package.<br />
*You need libsndfile and libsndfile-devel.<br />
*If you don't have a recent enough openldap, pass <code>--disable-openldap</code> to <code>autogen.sh</code> or <code>configure</code>.<br />
*You need neon and neon-devel.<br />
*You need qt3 and qt3-devel, or if you don't have the KDE development packages, pass <code>--disable-kde</code> to <code>autogen.sh</code> or <code>configure</code>.<br />
*You need mozilla-nss-devel.<br />
*In SuSE, you need gecko-sdk.<br />
<br />
=== download ===<br />
<br />
<p><br />
By the time you've upgraded your system to the point that it<br />
has all the packages you need to start building OO.o (mozilla etc. etc.) you're almost at the point that you<br />
can download the bulk of the source. To do this, after a<br />
successful configure simply type: <code>./download</code> and wait.<br />
</p><br />
<p><br />
If for whatever reason this fails, you can verify your download<br />
by fetching the equivalent .md5 file &amp; comparing it to<br />
the result of <code>md5sum <archive></code>. The source<br />
archives are http://go-ooo.org/packages/SRC680<br />
- put the source in ooo-build/src.<br />
</p><br />
<br />
=== make ===<br />
<br />
<p><br />
This is the taxing bit - type <code>make</code> and don't forget<br />
to press enter. Quite possibly you want to log the output, so<br />
why not <code>make 2>&1 | tee /tmp/log</code>.<br />
</p><br />
<p><br />
Since ooo-build wraps the actual OO.o configuration &amp;<br />
build process, there are a number of internal config checks that<br />
also need to pass. For a first time build it's well worth staying<br />
near the console while everything unpacks, and the internal<br />
configure runs; if that completes without incident - you're<br />
usually into the heavy-duty thumb twiddling.<br />
</p><br />
<br />
== See also ==<br />
<br />
*[[Installing]]<br />
*[[Tinderbox Setup]]<br />
*[[BuildSpeedup]]<br />
*[[OpenSUSE Build Instructions]]<br />
*[[Ubuntu Build Instructions]]<br />
*OpenOffice.org "Tools" page [http://tools.openoffice.org/dev_docs/build_linux.html]<br />
<br />
[[Category: Development]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11065Talk:Ubuntu Build Instructions2006-05-26T00:37:21Z<p>Kostmo: /* Failed Patches (HEAD) */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]] 10:24, 24 May 2006 (CEST))==<br />
===Failed Patches===<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
====HEAD====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
====ooo-build-2-0-2 (02:37, 26 May 2006 (CEST))====<br />
*ubuntu-dictionary.diff<br />
<br />
===Errors compiling ooo-build===<br />
====HEAD====<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====ooo-build-2-0-2 (02:35, 26 May 2006 (CEST))====<br />
<pre><br />
/home/kostmo/ooo-build/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/makedepend: error: makedepend: Failed to read file "hbox.cpp"<br />
dmake: Error code 1, while making '../unxlngi6.pro/misc/s_hbox.dpcc'<br />
dmake: '../unxlngi6.pro/misc/s_hbox.dpcc' removed.<br />
'---* TG_SLO.MK *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hwpfilter/source<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by gjc in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11064Talk:Ubuntu Build Instructions2006-05-26T00:35:25Z<p>Kostmo: /* Errors compiling HEAD ooo-build */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]] 10:24, 24 May 2006 (CEST))==<br />
====Failed Patches (HEAD)====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
===Errors compiling ooo-build===<br />
====HEAD====<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====ooo-build-2-0-2 (02:35, 26 May 2006 (CEST))====<br />
<pre><br />
/home/kostmo/ooo-build/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/makedepend: error: makedepend: Failed to read file "hbox.cpp"<br />
dmake: Error code 1, while making '../unxlngi6.pro/misc/s_hbox.dpcc'<br />
dmake: '../unxlngi6.pro/misc/s_hbox.dpcc' removed.<br />
'---* TG_SLO.MK *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hwpfilter/source<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by gjc in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11063Ubuntu Build Instructions2006-05-25T23:05:04Z<p>Kostmo: /* Development Environment Preparation Script */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant kdebase-dev<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ooo-build<br />
./autogen.sh --with-distro=Ubuntu<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
make<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11062Talk:Ubuntu Build Instructions2006-05-25T22:11:29Z<p>Kostmo: /* Failed Patches */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]] 10:24, 24 May 2006 (CEST))==<br />
====Failed Patches (HEAD)====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
====Errors compiling HEAD ooo-build====<br />
<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====Errors caused by gjc in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Talk:Ubuntu_Build_Instructions&diff=11061Talk:Ubuntu Build Instructions2006-05-25T22:10:35Z<p>Kostmo: /* Errors caused by running ''ubdatedb'' */</p>
<hr />
<div>==Build Problems ([[User:Kostmo|Kostmo]] 10:24, 24 May 2006 (CEST))==<br />
====Failed Patches====<br />
*disable-helpcontent2.diff<br />
*ubuntu-lpi.diff<br />
*ubuntu-dictionary.diff<br />
*fontconfig-substitute.diff<br />
<br />
I disabled them by commenting out their lines in <code>ooo-build/patches/src680/apply</code>.<br />
<br />
====Errors compiling HEAD ooo-build====<br />
<br />
With the above patches removed, the build process could commence. This error was obtained after about 3 hours into the build:<br />
<br />
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/star/help/HelpLinker<br />
dmake: Error code 1, while making '../../unxlngi6.pro/bin/smath_en-US.zip'<br />
'---* tg_merge.mk *---'<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/ooc680-m2/helpcontent2/util/smath<br />
make: *** [stamp/build] Error 1<br />
<br />
====Errors caused by gjc in ooo-build-2-0-2 (00:10, 26 May 2006 (CEST))====<br />
<pre><br />
BUILD FAILED<br />
/home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb/unxlngi6.pro/misc/build/hsqldb/build/build.xml:133: Error running gcj compiler<br />
<br />
Total time: 8 seconds<br />
dmake: Error code 1, while making './unxlngi6.pro/misc/build/so_built_so_hsqldb'<br />
'---* tg_merge.mk *---'<br />
<br />
ERROR: Error 65280 occurred while making /home/kostmo/ooo-build/build/OOO_2_0_2/hsqldb<br />
make: *** [stamp/build] Error 1<br />
</pre><br />
<br />
====Errors caused by running ''ubdatedb''====<br />
ERROR: cannot open /home/kostmo/ooo-build/build/ooc680-m2/connectivity/unxlngi6.pro/inc/com/sun/star/sdbc/XConnection.hdl for writing<br />
dmake: Error code 99, while making '../../unxlngi6.pro/inc/types_headergen.done'<br />
'---* tg_merge.mk *---'<br />
<br />
After the compiler aborts, I find that I can't write anything to the hard drive (e.g. save a text file to the desktop).</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11060Ubuntu Build Instructions2006-05-25T21:32:16Z<p>Kostmo: /* Additional Required Packages */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev (Ubuntu version is not high enough! 0.36.2 < 0.60)<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant kdebase-dev<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
make<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11059Ubuntu Build Instructions2006-05-25T21:28:37Z<p>Kostmo: /* Development Environment Preparation Script */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant kdebase-dev<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
make<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11058Ubuntu Build Instructions2006-05-25T21:19:30Z<p>Kostmo: /* Additional Required Packages */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
*libdbus-glib-1-dev<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
make<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=11003Ubuntu Build Instructions2006-05-25T11:52:06Z<p>Kostmo: /* Development Environment Preparation Script */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Development Environment Preparation Script===<br />
'''Note:''' User interaction is required first to enter a password for apt-get, and again much later to hit Enter when prompted for a CVS password.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev \<br />
tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev \<br />
libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers \<br />
libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "Preparations complete."<br />
<br />
cd ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
<br />
#Now comment out failing patch:<br />
cp patches/src680/apply patches/src680/apply~<br />
sed 's/^ubuntu-dictionary\.diff/#&/' <patches/src680/apply~ >patches/src680/apply<br />
rm patches/src680/apply~<br />
make<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=10999Ubuntu Build Instructions2006-05-25T10:53:03Z<p>Kostmo: /* Tips */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "Compilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Development Environment Preparation Script===<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "\n\nPreparations complete."<br />
<br />
cd ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
make<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=10998Ubuntu Build Instructions2006-05-25T10:50:36Z<p>Kostmo: /* Development Environment Preparation Script */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "\n\nCompilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Development Environment Preparation Script===<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 co -P ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "\n\nPreparations complete."<br />
<br />
cd ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
make<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=10993Ubuntu Build Instructions2006-05-25T10:39:20Z<p>Kostmo: /* Development Environment Preparation Script */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "\n\nCompilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Development Environment Preparation Script===<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers libaudio-dev libsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs co -P -z3 ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "\n\nPreparations complete."<br />
<br />
cd ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
make<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=10992Ubuntu Build Instructions2006-05-25T10:37:02Z<p>Kostmo: /* Development Environment Preparation Script */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "\n\nCompilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Development Environment Preparation Script===<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers libaudio-dev ibsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs co -P -z3 ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "\n\nPreparations complete."<br />
<br />
cd ooo-build<br />
./autogen.sh --with-distro=Ubuntu --disable-kde<br />
./download<br />
make<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=10991Ubuntu Build Instructions2006-05-25T10:35:24Z<p>Kostmo: /* Development Environment Preparation Script */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "\n\nCompilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Development Environment Preparation Script===<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev tcsh libcupsys2-dev java-gcj-compat-dev libarchive-zip-perl libjpeg62-dev libxml2-dev python-dev libdb4.3-dev libdb4.3-java-dev libcurl3-dev unixodbc-dev libldap2-dev mozilla-dev libnss-dev libsane-dev libxaw-headers libaudio-dev ibsndfile1-dev libneon24-dev libgnomevfs2-dev libstartup-notification0-dev ant<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs co -P -z3 ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "\n\nPreparations complete."<br />
<br />
cd ooo-build<br />
./autogen.sh --with-distro=Ubuntu<br />
./download<br />
make<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=10989Ubuntu Build Instructions2006-05-25T10:31:26Z<p>Kostmo: preparation script added</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "\n\nCompilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Development Environment Preparation Script===<br />
<pre><br />
#!/bin/bash<br />
echo "Starting Ubuntu ooo-build preparations..."<br />
<br />
sudo apt-get -y install cvs automake1.9 build-essential libpam0g-dev libpng12-dev flex bison libgtk2.0-dev<br />
<br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs co -P -z3 ooo-build<br />
cvs up -Pd -r ooo-build-2-0-2<br />
<br />
echo "\n\nPreparations complete."<br />
<br />
cd ooo-build<br />
./autogen.sh --with-distro=Ubuntu<br />
./download<br />
make<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=10987Ubuntu Build Instructions2006-05-25T10:29:40Z<p>Kostmo: /* Additional Required Packages */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
<br />
Far into the ''main build commencing'' section, you'll realize you need these:<br />
*?<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "\n\nCompilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=10983Ubuntu Build Instructions2006-05-25T10:22:32Z<p>Kostmo: /* Additional Required Packages */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
For <code>make</code> to finish its configuration stage, you need:<br />
*tcsh<br />
*libcupsys2-dev<br />
*java-gcj-compat-dev<br />
*libarchive-zip-perl<br />
*libjpeg62-dev<br />
*libxml2-dev<br />
*python-dev<br />
*libdb4.3-dev<br />
*libdb4.3-java-dev<br />
*libcurl3-dev<br />
*unixodbc-dev<br />
*libldap2-dev<br />
*mozilla-dev<br />
*libnss-dev<br />
*libsane-dev<br />
*libxaw-headers<br />
*libaudio-dev<br />
*libsndfile1-dev<br />
*libneon24-dev<br />
*libgnomevfs2-dev<br />
*kdebase-dev (KDE only?)<br />
*libstartup-notification0-dev<br />
*ant<br />
<br />
*??libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "\n\nCompilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=10970Ubuntu Build Instructions2006-05-25T08:48:32Z<p>Kostmo: /* Additional Required Packages */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
To obtain the source, you need:<br />
*cvs<br />
<br />
To complete <code>autogen.sh</code>, you need:<br />
*automake1.9<br />
*build-essential<br />
*libpam0g-dev<br />
*libpng12-dev<br />
*flex<br />
*bison<br />
*libgtk2.0-dev<br />
<br />
<br />
*libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "\n\nCompilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmohttps://wiki.openoffice.org/w/index.php?title=Ubuntu_Build_Instructions&diff=10969Ubuntu Build Instructions2006-05-25T08:30:23Z<p>Kostmo: /* Obtaining ooo-build */</p>
<hr />
<div>This tutorial will assume a stock [http://www.ubuntu.com/download Ubuntu] 5.10 (Breezy) system as a starting point.<br />
<br />
===Obtaining ooo-build===<br />
One may obtain the stable 2.0.2 version of <code>ooo-build</code> via CVS with the following commands:<br />
<pre><br />
export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'<br />
cvs login<br />
cvs -z3 checkout -P ooo-build<br />
cvs update -Pd -r ooo-build-2-0-2<br />
</pre><br />
You should then enter the <code>ooo-build</code> directory and run <code>./autogen.sh --with-distro=Ubuntu</code>. Most likely you'll also want to add the <code>--disable-kde</code> flag (unless you're using [http://www.kubuntu.org/ Kubuntu]).<br />
<br />
===Additional Required Packages===<br />
Packages may be obtained as follows:<br />
<br />
sudo apt-get install ''package_name [additional_package(s)]''<br />
<br />
*automake1.9<br />
*libmono-dev<br />
*''[please help populate the rest of this list!]''<br />
<br />
===Failed patches===<br />
Some of the patches listed in <code>ooo-build/patches/src680/apply</code> may not apply successfully. You can try to comment them out in the <code>apply</code> file, but this is an experimental solution...<br />
<br />
===Tips===<br />
A shell script like the one below will alert your attention upon completion of the quite lengthy build process. Run it after <code>./download</code> completes in place of <code>make</code>.<br />
<pre><br />
#!/bin/bash<br />
echo "Starting 'make' wrapper..."<br />
cd ~/ooo-build<br />
make<br />
echo "\n\nCompilation finished."<br />
mplayer -really-quiet ~/Music/My_Music_File.mp3<br />
</pre><br />
<br />
===Caveats===<br />
Don't do something silly like execute <code>udatedb</code> while <code>make</code> is in progress. This will result in locking the filesystem as read-only and cause the build to fail.<br />
<br />
==See also==<br />
*[[Building]]<br />
*[[Debug Build Problems]]<br />
<br />
<br />
[[Category: Distribution-Specific Build Instructions]]</div>Kostmo