Compilation problem

View: New views
7 Messages — Rating Filter:   Alert me  

Compilation problem

by Imre Steer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I am new on this list, please help me out with the problem I experienced
while trying to compile Openoffice at home.

I am following the directions here:
http://wiki.services.openoffice.org/wiki/Documentation/Building_Guide but
cannot get success.

I don't know where do I make a mistake here are the steps that I do:

1. Checking out the DEV300_m63 milestone source using mercurial as is
written in the guide - no problem

2. I realized that I must correct this issue before starting the
compilation:
http://qa.openoffice.org/issues/show_bug.cgi?id=106177
http://qa.openoffice.org/issues/show_bug.cgi?id=103269
I modified the problematic character by hand.

3. Run the configure script with the following switches:
./configure --with-use-shell=bash --with-system-libs --without-system-jars
--without-system-icu --without-system-agg --without-system-lpsolve
--without-system-mspack --enable-graphite=no --disable-mozilla

Also seems OK, no errors or warning message

3. Run the bootstrap script and set up the environment variables with the
LinuxX86Env.Set.sh and with:
export LOCALINSTALLDIR="/usr/local/ooo"
export PKGFORMAT="installed"

4. Started the build process with dmake

5. After about three hours the compilation finished, showed no error but I
cannot find the resulting executables in the given directory, only URE has
been put here.

This is a Debian Lenny linux with the necessary development libraries and
compilers from the official repository. I installed the newest JDK and ant
from the sun and apache website, they are also OK.


Any help would be appreciated,
Imre


I put the output of each step into logfile but it is huge, I only include
the end of it here, I think the problem is somewhere in the packaging step:

...

=============
Building module instsetoo_native
=============

Entering /usr/local/src/ooo/instsetoo_native/macosx
mkout -- version: 1.8
Nothing to build for OS LINUX and GUIBASE unx

Entering /usr/local/src/ooo/instsetoo_native/inc_openoffice/unix

Entering
/usr/local/src/ooo/instsetoo_native/inc_openoffice/windows/msi_languages

Entering /usr/local/src/ooo/instsetoo_native/util
cp -f /usr/local/src/ooo/solver/300/
unxlngi6.pro/pck/openoffice_nologo/intro.zip ../unxlngi6.pro/bin/intro.zip
cp -f /usr/local/src/ooo/solver/300/
unxlngi6.pro/pck/openoffice_dev_nologo/intro.zip ../
unxlngi6.pro/bin/dev/intro.zip
cp -f /usr/local/src/ooo/solver/300/
unxlngi6.pro/pck/broffice_nologo/intro.zip ../
unxlngi6.pro/bin/broffice/intro.zip
cp -f /usr/local/src/ooo/solver/300/
unxlngi6.pro/pck/broffice_dev_nologo/intro.zip ../
unxlngi6.pro/bin/broffice_dev/intro.zip
Using system python - nothing more to do here
Using system python - nothing more to do here
/usr/bin/perl -w /usr/local/src/ooo/solenv/bin/make_installer.pl -f
../util/openoffice.lst -l en-US -p OpenOffice -u ../unxlngi6.pro -buildid
9435 -msitemplate ../unxlngi6.pro/misc/openoffice/msi_templates -msilanguage
../unxlngi6.pro/misc/win_ulffiles -format installed
Subroutine installer::epmfile::getcwd redefined at
/usr/local/src/ooo/solenv/bin/modules/installer/epmfile.pm line 47
... checking environment variables ...

########################################################
make_installer.pl, version 1.0
Product list file: ../util/openoffice.lst
Taking setup script from solver
Unpackpath: /usr/local/src/ooo/instsetoo_native/util/../unxlngi6.pro
Compiler: unxlngi6
Product: OpenOffice
BuildID: 9435
Build: DEV300
No minor set
Product version
Using default installpath
Package format: installed
msi templatepath: /usr/local/src/ooo/instsetoo_native/util/../
unxlngi6.pro/misc/openoffice/msi_templates
msi template path will be ignored for non Windows builds!
msi languagepath: /usr/local/src/ooo/instsetoo_native/util/../
unxlngi6.pro/misc/win_ulffiles
msi language path will be ignored for non Windows builds!
Calling epm
Stripping files
Unzip ARCHIVE files
services.rdb can be created
Languages:
    en-US
########################################################
... checking required files ...
...... searching zip ...
    Found: /usr/bin/zip
... analyzing ../util/openoffice.lst ...
... reading include pathes ...
... analyzing script: /usr/local/src/ooo/solver/300/
unxlngi6.pro/bin/setup_osl.ins ...
... analyzing directories ...
... analyzing files ...
... analyzing scpactions ...
... analyzing shortcuts ...
... analyzing unix links ...
... analyzing profile ...
... analyzing profileitems ...
... analyzing modules ...
------------------------------------
... languages en-US ...
... analyzing files ...
... analyzing files with flag ARCHIVE ...
... analyzing files with flag SUBST_FILENAME ...
... analyzing files with flag SCPZIP_REPLACE ...
... analyzing files with flag PATCH_SO_NAME ...
... analyzing files with flag HIDDEN ...
... creating preregistered services.rdb ...
javavm.uno.so
javaloader.uno.so
stocservices.uno.so
javavm.uno.so
javaloader.uno.so
stocservices.uno.so
... merging files into registry database ...
... analyzing all directories for this product ...
... analyzing links ...
... analyzing unix links ...
... creating profiles ...
... analyzing modules ...
... creating installation directory ...
... creating installation set in /usr/local/ooo ...
... removing old installation directories ...
... creating directories ...
... copying files ...
... creating links ...
... registering extensions ...
... current dir: /usr/local/ooo_inprogress/openoffice.org3/program ...
... unopkg add --shared --verbose ../share/extension/install/dict-en.oxt
-env:UserInstallation=file:///tmp/ooopackaging/i_160301257106573/
unxlngi6.pro/OpenOffice/installed/uno/en-US 2>&1 | ...
... unopkg add --shared --verbose ../share/extension/install/dict-es.oxt
-env:UserInstallation=file:///tmp/ooopackaging/i_160301257106573/
unxlngi6.pro/OpenOffice/installed/uno/en-US 2>&1 | ...
... unopkg add --shared --verbose ../share/extension/install/dict-fr.oxt
-env:UserInstallation=file:///tmp/ooopackaging/i_160301257106573/
unxlngi6.pro/OpenOffice/installed/uno/en-US 2>&1 | ...
... cleaning the output tree ...
... removing directory /tmp/ooopackaging/i_160301257106573 ...
... removing directory /usr/local/src/ooo/instsetoo_native/
unxlngi6.pro/OpenOffice/installed/stripped/en-US ...
... checking log file /usr/local/src/ooo/instsetoo_native/
unxlngi6.pro/OpenOffice/installed/logging/en-US/log_DEV300_en-US.log

***********************************************************
Successful packaging process!
***********************************************************
... creating log file log_DEV300_en-US.log
Sun Nov  1 21:17:35 2009 (01:22 min.)
/usr/bin/perl -w /usr/local/src/ooo/solenv/bin/gen_update_info.pl --buildid
9435 --arch "x86" --os "Linux" --lstfile ../util/openoffice.lst --product
OpenOffice --languages en-US ../util/update.xml > ../
unxlngi6.pro/misc/openoffice_en-US_Linux_x86.installed.update.xml
/usr/bin/perl -w /usr/local/src/ooo/solenv/bin/make_installer.pl -f
../util/openoffice.lst -l en-US -p OpenOffice_SDK -u
../unxlngi6.pro-buildid 9435 -msitemplate ../
unxlngi6.pro/misc/sdkoo/msi_templates -msilanguage ../
unxlngi6.pro/misc/win_ulffiles -dontstrip -format installed
Subroutine installer::epmfile::getcwd redefined at
/usr/local/src/ooo/solenv/bin/modules/installer/epmfile.pm line 47
... checking environment variables ...

########################################################
make_installer.pl, version 1.0
Product list file: ../util/openoffice.lst
Taking setup script from solver
Unpackpath: /usr/local/src/ooo/instsetoo_native/util/../unxlngi6.pro
Compiler: unxlngi6
Product: OpenOffice_SDK
BuildID: 9435
Build: DEV300
No minor set
Product version
Using default installpath
Package format: installed
msi templatepath: /usr/local/src/ooo/instsetoo_native/util/../
unxlngi6.pro/misc/sdkoo/msi_templates
msi template path will be ignored for non Windows builds!
msi languagepath: /usr/local/src/ooo/instsetoo_native/util/../
unxlngi6.pro/misc/win_ulffiles
msi language path will be ignored for non Windows builds!
Calling epm
No file stripping
Unzip ARCHIVE files
services.rdb can be created
Languages:
    en-US
########################################################
... checking required files ...
...... searching zip ...
    Found: /usr/bin/zip
... analyzing ../util/openoffice.lst ...
... reading include pathes ...
... analyzing script: /usr/local/src/ooo/solver/300/
unxlngi6.pro/bin/sdkoo.ins ...
... analyzing directories ...
... analyzing files ...
... analyzing scpactions ...
... analyzing shortcuts ...
... analyzing unix links ...
... analyzing profile ...
... analyzing profileitems ...
... analyzing modules ...
------------------------------------
... languages en-US ...
... analyzing files ...
... analyzing files with flag ARCHIVE ...
... analyzing files with flag SUBST_FILENAME ...
... analyzing files with flag SCPZIP_REPLACE ...
... analyzing files with flag PATCH_SO_NAME ...
... analyzing files with flag HIDDEN ...
... merging files into registry database ...
... analyzing all directories for this product ...
... analyzing links ...
... analyzing unix links ...
... creating profiles ...
... analyzing modules ...
... creating installation directory ...
... creating installation set in /usr/local/ooo ...
... removing old installation directories ...
... creating directories ...
... copying files ...
... creating links ...
... registering extensions ...
readdir() attempted on invalid dirhandle DIR at
/usr/local/src/ooo/solenv/bin/modules/installer/systemactions.pm line 925.
closedir() attempted on invalid dirhandle DIR at
/usr/local/src/ooo/solenv/bin/modules/installer/systemactions.pm line 926.
... cleaning the output tree ...
... removing directory /tmp/ooopackaging/i_262571257106656 ...
... checking log file /usr/local/src/ooo/instsetoo_native/
unxlngi6.pro/OpenOffice_SDK/installed/logging/en-US/log_DEV300_en-US.log

***********************************************************
Successful packaging process!
***********************************************************
... creating log file log_DEV300_en-US.log
Sun Nov  1 21:20:07 2009 (02:31 min.)
/usr/bin/perl -w /usr/local/src/ooo/solenv/bin/make_installer.pl -f
../util/openoffice.lst \
        -l en-US -p URE -u ../unxlngi6.pro -buildid 9435 -format installed
\
        -msitemplate ../unxlngi6.pro/misc/ure/msi_templates \
        -msilanguage ../unxlngi6.pro/misc/win_ulffiles
Subroutine installer::epmfile::getcwd redefined at
/usr/local/src/ooo/solenv/bin/modules/installer/epmfile.pm line 47
... checking environment variables ...

########################################################
make_installer.pl, version 1.0
Product list file: ../util/openoffice.lst
Taking setup script from solver
Unpackpath: /usr/local/src/ooo/instsetoo_native/util/../unxlngi6.pro
Compiler: unxlngi6
Product: URE
BuildID: 9435
Build: DEV300
No minor set
Product version
Using default installpath
Package format: installed
msi templatepath: /usr/local/src/ooo/instsetoo_native/util/../
unxlngi6.pro/misc/ure/msi_templates
msi template path will be ignored for non Windows builds!
msi languagepath: /usr/local/src/ooo/instsetoo_native/util/../
unxlngi6.pro/misc/win_ulffiles
msi language path will be ignored for non Windows builds!
Calling epm
Stripping files
Unzip ARCHIVE files
services.rdb can be created
Languages:
    en-US
########################################################
... checking required files ...
...... searching zip ...
    Found: /usr/bin/zip
... analyzing ../util/openoffice.lst ...
... reading include pathes ...
... analyzing script: /usr/local/src/ooo/solver/300/unxlngi6.pro/bin/ure.ins...
... analyzing directories ...
... analyzing files ...
... analyzing scpactions ...
... analyzing shortcuts ...
... analyzing unix links ...
... analyzing profile ...
... analyzing profileitems ...
... analyzing modules ...
------------------------------------
... languages en-US ...
... analyzing files ...
... analyzing files with flag ARCHIVE ...
... analyzing files with flag SUBST_FILENAME ...
... analyzing files with flag SCPZIP_REPLACE ...
... analyzing files with flag PATCH_SO_NAME ...
... analyzing files with flag HIDDEN ...
... creating preregistered services.rdb ...
javavm.uno.so
javaloader.uno.so
stocservices.uno.so
... merging files into registry database ...
... analyzing all directories for this product ...
... analyzing links ...
... analyzing unix links ...
... creating profiles ...
... analyzing modules ...
... creating installation directory ...
... creating installation set in /usr/local/ooo ...
... removing old installation directories ...
... creating directories ...
... copying files ...
... creating links ...
... registering extensions ...
readdir() attempted on invalid dirhandle DIR at
/usr/local/src/ooo/solenv/bin/modules/installer/systemactions.pm line 925.
closedir() attempted on invalid dirhandle DIR at
/usr/local/src/ooo/solenv/bin/modules/installer/systemactions.pm line 926.
... cleaning the output tree ...
... removing directory /tmp/ooopackaging/i_243941257106807 ...
... removing directory /usr/local/src/ooo/instsetoo_native/
unxlngi6.pro/URE/installed/stripped/en-US ...
... checking log file /usr/local/src/ooo/instsetoo_native/
unxlngi6.pro/URE/installed/logging/en-US/log_DEV300_en-US.log

***********************************************************
Successful packaging process!
***********************************************************
... creating log file log_DEV300_en-US.log
Sun Nov  1 21:20:09 2009 (00:02 min.)

Re: Compilation problem

by Stephan Bergmann :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 11/02/09 14:02, Imre Steer wrote:
> 3. Run the bootstrap script and set up the environment variables with the
> LinuxX86Env.Set.sh and with:
> export LOCALINSTALLDIR="/usr/local/ooo"
> export PKGFORMAT="installed"
[...]
> 5. After about three hours the compilation finished, showed no error but I
> cannot find the resulting executables in the given directory, only URE has
> been put here.

I assume what happens is the following:  Per
instsetoo_native/util/makefile.mk, three products are built by default,
openoffice_en-US, sdkoo_en-US, and ure_en-US.  If each builds into
$LOCALINSTALLDIR, and presumably removes the directory before installing
into it, the net effect would be to have just URE (the product that
happens to be built last) afterwards.  (Also, if you did a parallel
build, you would probably get even more funny results.)

There is logic in that makefile.mk to only build openoffice (and not the
other two products) if the BUILD_TYPE env var does not contain a "ODK"
token (presumably controlled through some ./configure switch).  That
would suggest one way solve this for you (another is to simply first
make a complete build without LOCALINSTALLDIR and PKGFORMAT, then cd
instsetoo_native/util && dmake with the two vars set).

-Stephan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: Compilation problem

by bjoern michaelsen - Sun Microsystems - Hamburg Germany :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Mon, 02 Nov 2009 14:40:31 +0100
Stephan Bergmann <Stephan.Bergmann@...> wrote:

> On 11/02/09 14:02, Imre Steer wrote:
> > 3. Run the bootstrap script and set up the environment variables
> > with the LinuxX86Env.Set.sh and with:
> > export LOCALINSTALLDIR="/usr/local/ooo"
> > export PKGFORMAT="installed"
> [...]
> > 5. After about three hours the compilation finished, showed no
> > error but I cannot find the resulting executables in the given
> > directory, only URE has been put here.
>
> I assume what happens is the following:  Per
> instsetoo_native/util/makefile.mk, three products are built by
> default, openoffice_en-US, sdkoo_en-US, and ure_en-US.  If each
> builds into $LOCALINSTALLDIR, and presumably removes the directory
> before installing into it, the net effect would be to have just URE
> (the product that happens to be built last) afterwards.  (Also, if
> you did a parallel build, you would probably get even more funny
> results.)

Is there a bug for this? If not, I think we should create one. This is
really confusing for newcomers. For now, I removed PKGFORMAT=installed
from the Building Guide. FORCE2ARCHIVE should do for now.

Best Regards,

Bjoern

--
===========================================================================
 Sitz der Gesellschaft:
 Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
 Amtsgericht Muenchen: HRB 161028
 Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel
 Vorsitzender des Aufsichtsrates: Martin Haering
===========================================================================


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: Compilation problem

by Imre Steer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello guys,

Thanks for the quick response, I will try these and I think it will be OK.


Kind regards,
Imre

2009/11/2 bjoern michaelsen - Sun Microsystems - Hamburg Germany <
bjoern.michaelsen@...>

> On Mon, 02 Nov 2009 14:40:31 +0100
> Stephan Bergmann <Stephan.Bergmann@...> wrote:
>
> > On 11/02/09 14:02, Imre Steer wrote:
> > > 3. Run the bootstrap script and set up the environment variables
> > > with the LinuxX86Env.Set.sh and with:
> > > export LOCALINSTALLDIR="/usr/local/ooo"
> > > export PKGFORMAT="installed"
> > [...]
> > > 5. After about three hours the compilation finished, showed no
> > > error but I cannot find the resulting executables in the given
> > > directory, only URE has been put here.
> >
> > I assume what happens is the following:  Per
> > instsetoo_native/util/makefile.mk, three products are built by
> > default, openoffice_en-US, sdkoo_en-US, and ure_en-US.  If each
> > builds into $LOCALINSTALLDIR, and presumably removes the directory
> > before installing into it, the net effect would be to have just URE
> > (the product that happens to be built last) afterwards.  (Also, if
> > you did a parallel build, you would probably get even more funny
> > results.)
>
> Is there a bug for this? If not, I think we should create one. This is
> really confusing for newcomers. For now, I removed PKGFORMAT=installed
> from the Building Guide. FORCE2ARCHIVE should do for now.
>
> Best Regards,
>
> Bjoern
>
> --
> ===========================================================================
>  Sitz der Gesellschaft:
>  Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
>  Amtsgericht Muenchen: HRB 161028
>  Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel
>  Vorsitzender des Aufsichtsrates: Martin Haering
> ===========================================================================
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

Re: Compilation problem

by Ingo Schmidt :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,

LOCALINSTALLDIR was not created for this situation. Typically you can
use PKGFORMAT=installed without any problem. You will get all
installation sets in the output of instsetoo_native, the same way you
will get the RPMs or the tar.gz files. In instsetoo_native you have the
productname in the path to the installation set, so that there is no
conflict. This works for all package formats, for "rpm", for "archive"
and for "installed". But if you use LOCALINSTALLDIR, you break the
standard output directory, because you decide, where the installation
set shall be located. And if you build three installation sets, all
three are of course created into LOCALINSTALLDIR. Of course we can add
the productname automatically to LOCALINSTALLDIR, but this fails, if you
build OOo in French after OOo in English. So adding the language would
also be necessary.
So please use LOCALINSTALLDIR only, if you create one specified
installation set. By the way, FORCE2ARCHIVE forces the package format to
"archive", which is pretty the same as "installed", but only compresses
the content at the end. So please feel free to use "installed", but not
in combination with LOCALINSTALLDIR. Use LOCALINSTALLDIR not as default,
but only, if you want to create the installation set at a specified
location.
Regards

   Ingo


On 11/02/09 16:34, Imre Steer wrote:

> Hello guys,
>
> Thanks for the quick response, I will try these and I think it will be OK.
>
>
> Kind regards,
> Imre
>
> 2009/11/2 bjoern michaelsen - Sun Microsystems - Hamburg Germany <
> bjoern.michaelsen@...>
>
>> On Mon, 02 Nov 2009 14:40:31 +0100
>> Stephan Bergmann <Stephan.Bergmann@...> wrote:
>>
>>> On 11/02/09 14:02, Imre Steer wrote:
>>>> 3. Run the bootstrap script and set up the environment variables
>>>> with the LinuxX86Env.Set.sh and with:
>>>> export LOCALINSTALLDIR="/usr/local/ooo"
>>>> export PKGFORMAT="installed"
>>> [...]
>>>> 5. After about three hours the compilation finished, showed no
>>>> error but I cannot find the resulting executables in the given
>>>> directory, only URE has been put here.
>>> I assume what happens is the following:  Per
>>> instsetoo_native/util/makefile.mk, three products are built by
>>> default, openoffice_en-US, sdkoo_en-US, and ure_en-US.  If each
>>> builds into $LOCALINSTALLDIR, and presumably removes the directory
>>> before installing into it, the net effect would be to have just URE
>>> (the product that happens to be built last) afterwards.  (Also, if
>>> you did a parallel build, you would probably get even more funny
>>> results.)
>> Is there a bug for this? If not, I think we should create one. This is
>> really confusing for newcomers. For now, I removed PKGFORMAT=installed
>> from the Building Guide. FORCE2ARCHIVE should do for now.
>>
>> Best Regards,
>>
>> Bjoern
>>
>> --
>> ===========================================================================
>>  Sitz der Gesellschaft:
>>  Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
>>  Amtsgericht Muenchen: HRB 161028
>>  Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel
>>  Vorsitzender des Aufsichtsrates: Martin Haering
>> ===========================================================================
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: Compilation problem

by Imre Steer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello Ingo,

Thanks, I will go this way first.


Regards,
Imre

2009/11/2 Ingo Schmidt - Sun Germany - ham02 - Hamburg <Ingo.Schmidt@...
>

> Hello,
>
> LOCALINSTALLDIR was not created for this situation. Typically you can use
> PKGFORMAT=installed without any problem. You will get all installation sets
> in the output of instsetoo_native, the same way you will get the RPMs or the
> tar.gz files. In instsetoo_native you have the productname in the path to
> the installation set, so that there is no conflict. This works for all
> package formats, for "rpm", for "archive" and for "installed". But if you
> use LOCALINSTALLDIR, you break the standard output directory, because you
> decide, where the installation set shall be located. And if you build three
> installation sets, all three are of course created into LOCALINSTALLDIR. Of
> course we can add the productname automatically to LOCALINSTALLDIR, but this
> fails, if you build OOo in French after OOo in English. So adding the
> language would also be necessary.
> So please use LOCALINSTALLDIR only, if you create one specified
> installation set. By the way, FORCE2ARCHIVE forces the package format to
> "archive", which is pretty the same as "installed", but only compresses the
> content at the end. So please feel free to use "installed", but not in
> combination with LOCALINSTALLDIR. Use LOCALINSTALLDIR not as default, but
> only, if you want to create the installation set at a specified location.
> Regards
>
>  Ingo
>
>
>
> On 11/02/09 16:34, Imre Steer wrote:
>
>> Hello guys,
>>
>> Thanks for the quick response, I will try these and I think it will be OK.
>>
>>
>> Kind regards,
>> Imre
>>
>> 2009/11/2 bjoern michaelsen - Sun Microsystems - Hamburg Germany <
>> bjoern.michaelsen@...>
>>
>>  On Mon, 02 Nov 2009 14:40:31 +0100
>>> Stephan Bergmann <Stephan.Bergmann@...> wrote:
>>>
>>>  On 11/02/09 14:02, Imre Steer wrote:
>>>>
>>>>> 3. Run the bootstrap script and set up the environment variables
>>>>> with the LinuxX86Env.Set.sh and with:
>>>>> export LOCALINSTALLDIR="/usr/local/ooo"
>>>>> export PKGFORMAT="installed"
>>>>>
>>>> [...]
>>>>
>>>>> 5. After about three hours the compilation finished, showed no
>>>>> error but I cannot find the resulting executables in the given
>>>>> directory, only URE has been put here.
>>>>>
>>>> I assume what happens is the following:  Per
>>>> instsetoo_native/util/makefile.mk, three products are built by
>>>> default, openoffice_en-US, sdkoo_en-US, and ure_en-US.  If each
>>>> builds into $LOCALINSTALLDIR, and presumably removes the directory
>>>> before installing into it, the net effect would be to have just URE
>>>> (the product that happens to be built last) afterwards.  (Also, if
>>>> you did a parallel build, you would probably get even more funny
>>>> results.)
>>>>
>>> Is there a bug for this? If not, I think we should create one. This is
>>> really confusing for newcomers. For now, I removed PKGFORMAT=installed
>>> from the Building Guide. FORCE2ARCHIVE should do for now.
>>>
>>> Best Regards,
>>>
>>> Bjoern
>>>
>>> --
>>>
>>> ===========================================================================
>>>  Sitz der Gesellschaft:
>>>  Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
>>>  Amtsgericht Muenchen: HRB 161028
>>>  Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel
>>>  Vorsitzender des Aufsichtsrates: Martin Haering
>>>
>>> ===========================================================================
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

Re: Compilation problem

by Imre Steer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,

I am beginning to understand the directory structure of the project :-). And
yes, the last build was successful, scalc is now running on my desktop.

Thank you all for the help, it saved me days of struggling.



Regards,
Imre





> 2009/11/2 Ingo Schmidt - Sun Germany - ham02 - Hamburg <
> Ingo.Schmidt@...>
>
> Hello,
>>
>> LOCALINSTALLDIR was not created for this situation. Typically you can use
>> PKGFORMAT=installed without any problem. You will get all installation sets
>> in the output of instsetoo_native, the same way you will get the RPMs or the
>> tar.gz files. In instsetoo_native you have the productname in the path to
>> the installation set, so that there is no conflict. This works for all
>> package formats, for "rpm", for "archive" and for "installed". But if you
>> use LOCALINSTALLDIR, you break the standard output directory, because you
>> decide, where the installation set shall be located. And if you build three
>> installation sets, all three are of course created into LOCALINSTALLDIR. Of
>> course we can add the productname automatically to LOCALINSTALLDIR, but this
>> fails, if you build OOo in French after OOo in English. So adding the
>> language would also be necessary.
>> So please use LOCALINSTALLDIR only, if you create one specified
>> installation set. By the way, FORCE2ARCHIVE forces the package format to
>> "archive", which is pretty the same as "installed", but only compresses the
>> content at the end. So please feel free to use "installed", but not in
>> combination with LOCALINSTALLDIR. Use LOCALINSTALLDIR not as default, but
>> only, if you want to create the installation set at a specified location.
>> Regards
>>
>>  Ingo
>>
>>