Re: [gentoo-user] OpenOffice build failed

Re: [gentoo-user] OpenOffice build failed

[Meino Christian Cramer]

Hi,

 first of all: A BIG thank you to all that send replies to my initial
 cry. :)

 The real reason behind the unsuccessful build of OpenOffice was a
 wrong PYTHONPATH, which I had fixed in the user settings but not for
 the root account. They were rests from older settings, which I had
 took over when starting with Gentoo.

 The current build took five hours to finish, the CPU does not exceeds
 a core temperature of 45.5 degree celsius and the 9.1 GByte on /tmp
 were enough. Now I will remove the temporary installed symlink from
 /var/tmp/portage.

 Openoffice runs well in a quick test.

 Thank you again for all your help!
 Kind regards,
 Meino



 PS: May be it would be an idea to run a "system sanity check script"
 before such megabuilds, which quickly not only checks for missing
 software dependencies (which is already done) but also for a clean
 environment AND STOP the build, if anything is wrong.

 For example: An automatic echo on the console like "found only
 5GBytes (need 9GBytes) on /var/tmp/portage ...you have 3 seconds to
 abort with ^C or I will continue" will not help for psychological
 reasons: One who starts such a megabuild (and knows it will run for
 hours) will press <RETURN> after the specific command and will go to
 bed.

 My suggestion would be to abort hard at once and only when given with
 option "-f space" (force) will ignore _only_ the warning about
 missing free space on hd. Other warnings will still be able to abort.

 This way, the PYTHONPATH problem would have been discovered right in
 the start phase and not after the whole build process when it comes
 to the install process.

 Only my two cents -- your mileage may vary.
 Keep hacking!
 Meino

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] OpenOffice build failed.

[Meino Christian Cramer]

Hi,

 I tried to build OpenOffice from source. After hours of copmiling it
 fails with:

    Cleaning /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice
   Building /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/ooo-wrapper2
   Generating man page ...
   Building /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/install-dict
   Building /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/program/java-set-classpath
   Building /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/program/pyunorc-update64
   Installing extra en-US templates ...
   Installing system files ...
   Execute ooinstall ...
   Reading setup from ./setup
   Sucking env from build setup
   Use of uninitialized value in string eq at ./ooinstall line 58.
   Performing environment substitutions ...
   Setting up environment
   Running installer
   ... checking environment variables ...
   
   ########################################################
   make_installer.pl, version 1.0
   Product list file: openoffice.lst
   Taking setup script from solver
   Unpackpath: /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util
   Compiler: unxlngi6
   Product: OpenOffice
   BuildID: 9011
   Build: OOB680
   No minor set
   Product version
   Installpath: /usr/lib/openoffice
   Package format: native
   Package list file: ../inc_openoffice/unix/packagelist.txt
   Addon-Package list file: ../inc_openoffice/unix/packagelist_language.txt
   Not 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
   ...... searching unzip ...
           Found: /usr/bin/unzip
   ... analyzing openoffice.lst ...
   ... analyzing script: /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/setup_osl.ins ...
   ... analyzing directories ...
   ... analyzing files ...
   ... analyzing scpactions ...
   ... analyzing shortcuts ...
   ... analyzing profile ...
   ... analyzing profileitems ...
   ... analyzing modules ...
   ------------------------------------
   ... languages en-US ...
   ... analyzing files ...
   ... analyzing files with flag ARCHIVE ...
   ... analyzing files with flag SCPZIP_REPLACE ...
   ... analyzing files with flag PATCH_SO_NAME ...
   ... creating preregistered services.rdb ...
   
   **************************************************
   ERROR: ERROR: Could not register all components!
   in function: create_services_rdb
   **************************************************
   
   **************************************************
   ERROR: Saved logfile: /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//logging/en-US/log_OOB680__en-US.log
   **************************************************
   ... cleaning the output tree ...
   ... removing directory /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//zip/en-US ...
   ... removing directory /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//services.rdb/en-US_witherror_1 ...
   Thu May 25 02:36:02 2006 (00:36 min.)
   Failed to install: Bad file descriptor at ./ooinstall line 129.
   make: *** [install] Error 1

 
 What did I so badly wrong here ?

 Kind regards,
 mcc

 PS: I symlinked /var/tmp/portags to /tmp/portage (I carefully copied
 all permissions settings...) due to space problems.

 
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Jeff]

Good Lord man... why would you want to compile OO from source?

emerge openoffice-bin

:-)

Meino Christian Cramer wrote:
> Hi,
> 
>  I tried to build OpenOffice from source. After hours of copmiling it
>  fails with:
> 
>     Cleaning /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice
>    Building /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/ooo-wrapper2
>    Generating man page ...
>    Building /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/install-dict
>    Building /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/program/java-set-classpath
>    Building /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/program/pyunorc-update64
>    Installing extra en-US templates ...
>    Installing system files ...
>    Execute ooinstall ...
>    Reading setup from ./setup
>    Sucking env from build setup
>    Use of uninitialized value in string eq at ./ooinstall line 58.
>    Performing environment substitutions ...
>    Setting up environment
>    Running installer
>    ... checking environment variables ...
>    
>    ########################################################
>    make_installer.pl, version 1.0
>    Product list file: openoffice.lst
>    Taking setup script from solver
>    Unpackpath: /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util
>    Compiler: unxlngi6
>    Product: OpenOffice
>    BuildID: 9011
>    Build: OOB680
>    No minor set
>    Product version
>    Installpath: /usr/lib/openoffice
>    Package format: native
>    Package list file: ../inc_openoffice/unix/packagelist.txt
>    Addon-Package list file: ../inc_openoffice/unix/packagelist_language.txt
>    Not 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
>    ...... searching unzip ...
>            Found: /usr/bin/unzip
>    ... analyzing openoffice.lst ...
>    ... analyzing script: /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/setup_osl.ins ...
>    ... analyzing directories ...
>    ... analyzing files ...
>    ... analyzing scpactions ...
>    ... analyzing shortcuts ...
>    ... analyzing profile ...
>    ... analyzing profileitems ...
>    ... analyzing modules ...
>    ------------------------------------
>    ... languages en-US ...
>    ... analyzing files ...
>    ... analyzing files with flag ARCHIVE ...
>    ... analyzing files with flag SCPZIP_REPLACE ...
>    ... analyzing files with flag PATCH_SO_NAME ...
>    ... creating preregistered services.rdb ...
>    
>    **************************************************
>    ERROR: ERROR: Could not register all components!
>    in function: create_services_rdb
>    **************************************************
>    
>    **************************************************
>    ERROR: Saved logfile: /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//logging/en-US/log_OOB680__en-US.log
>    **************************************************
>    ... cleaning the output tree ...
>    ... removing directory /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//zip/en-US ...
>    ... removing directory /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//services.rdb/en-US_witherror_1 ...
>    Thu May 25 02:36:02 2006 (00:36 min.)
>    Failed to install: Bad file descriptor at ./ooinstall line 129.
>    make: *** [install] Error 1
> 
>  
>  What did I so badly wrong here ?
> 
>  Kind regards,
>  mcc
> 
>  PS: I symlinked /var/tmp/portags to /tmp/portage (I carefully copied
>  all permissions settings...) due to space problems.
> 
>  
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Meino Christian Cramer]

From: Jeff <jmg_071769@comcast.net>
Subject: Re: [gentoo-user] OpenOffice build failed.
Date: Thu, 25 May 2006 00:17:27 -0400

> Good Lord man... why would you want to compile OO from source?

 Since gentoo offers this...

 Or in other words:
 Why does gentoo offer it, if one needs to be god to get it run ???
 :)



> 
> emerge openoffice-bin
> 
> :-)
> 
> Meino Christian Cramer wrote:
> > Hi,
> > 
> >  I tried to build OpenOffice from source. After hours of copmiling it
> >  fails with:
> > 
> >     Cleaning /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice
> >    Building /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/ooo-wrapper2
> >    Generating man page ...
> >    Building /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/install-dict
> >    Building /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/program/java-set-classpath
> >    Building /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/program/pyunorc-update64
> >    Installing extra en-US templates ...
> >    Installing system files ...
> >    Execute ooinstall ...
> >    Reading setup from ./setup
> >    Sucking env from build setup
> >    Use of uninitialized value in string eq at ./ooinstall line 58.
> >    Performing environment substitutions ...
> >    Setting up environment
> >    Running installer
> >    ... checking environment variables ...
> >    
> >    ########################################################
> >    make_installer.pl, version 1.0
> >    Product list file: openoffice.lst
> >    Taking setup script from solver
> >    Unpackpath: /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util
> >    Compiler: unxlngi6
> >    Product: OpenOffice
> >    BuildID: 9011
> >    Build: OOB680
> >    No minor set
> >    Product version
> >    Installpath: /usr/lib/openoffice
> >    Package format: native
> >    Package list file: ../inc_openoffice/unix/packagelist.txt
> >    Addon-Package list file: ../inc_openoffice/unix/packagelist_language.txt
> >    Not 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
> >    ...... searching unzip ...
> >            Found: /usr/bin/unzip
> >    ... analyzing openoffice.lst ...
> >    ... analyzing script: /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/setup_osl.ins ...
> >    ... analyzing directories ...
> >    ... analyzing files ...
> >    ... analyzing scpactions ...
> >    ... analyzing shortcuts ...
> >    ... analyzing profile ...
> >    ... analyzing profileitems ...
> >    ... analyzing modules ...
> >    ------------------------------------
> >    ... languages en-US ...
> >    ... analyzing files ...
> >    ... analyzing files with flag ARCHIVE ...
> >    ... analyzing files with flag SCPZIP_REPLACE ...
> >    ... analyzing files with flag PATCH_SO_NAME ...
> >    ... creating preregistered services.rdb ...
> >    
> >    **************************************************
> >    ERROR: ERROR: Could not register all components!
> >    in function: create_services_rdb
> >    **************************************************
> >    
> >    **************************************************
> >    ERROR: Saved logfile: /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//logging/en-US/log_OOB680__en-US.log
> >    **************************************************
> >    ... cleaning the output tree ...
> >    ... removing directory /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//zip/en-US ...
> >    ... removing directory /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//services.rdb/en-US_witherror_1 ...
> >    Thu May 25 02:36:02 2006 (00:36 min.)
> >    Failed to install: Bad file descriptor at ./ooinstall line 129.
> >    make: *** [install] Error 1
> > 
> >  
> >  What did I so badly wrong here ?
> > 
> >  Kind regards,
> >  mcc
> > 
> >  PS: I symlinked /var/tmp/portags to /tmp/portage (I carefully copied
> >  all permissions settings...) due to space problems.
> > 
> >  
> -- 
> gentoo-user@gentoo.org mailing list
> 
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Richard Broersma Jr]

I was having problems getting OO to build.  I issued the following bug report. 
http://bugs.gentoo.org/show_bug.cgi?id=126937

In my case the it was due to a hardware issue.  I kept retrying the emerge and at last it
succeeded (on a very very cold evening...).  My best guess is that the large volume of builds was
causing my CPU to over heat.  This guess was bolster by the fact that I am able to get consistent
successful builds of OO when I pull of the computer's case and direct a cooling fan on the
computers internals. :-)

I realize my "fix/work around" might not sit well with most people.  But in my defense, it is just
a toy computer that I have fun tinkering around with.

--- Meino Christian Cramer <Meino.Cramer@gmx.de> wrote:

> From: Jeff <jmg_071769@comcast.net>
> Subject: Re: [gentoo-user] OpenOffice build failed.
> Date: Thu, 25 May 2006 00:17:27 -0400
> 
> > Good Lord man... why would you want to compile OO from source?
> 
>  Since gentoo offers this...
> 
>  Or in other words:
>  Why does gentoo offer it, if one needs to be god to get it run ???
>  :)
> 
> 
> 
> > 
> > emerge openoffice-bin
> > 
> > :-)
> > 
> > Meino Christian Cramer wrote:
> > > Hi,
> > > 
> > >  I tried to build OpenOffice from source. After hours of copmiling it
> > >  fails with:
> > > 
> > >     Cleaning /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice
> > >    Building /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/ooo-wrapper2
> > >    Generating man page ...
> > >    Building /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/install-dict
> > >    Building
> /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/program/java-set-classpath
> > >    Building
> /var/tmp/portage/openoffice-2.0.2-r1/image//usr/lib/openoffice/program/pyunorc-update64
> > >    Installing extra en-US templates ...
> > >    Installing system files ...
> > >    Execute ooinstall ...
> > >    Reading setup from ./setup
> > >    Sucking env from build setup
> > >    Use of uninitialized value in string eq at ./ooinstall line 58.
> > >    Performing environment substitutions ...
> > >    Setting up environment
> > >    Running installer
> > >    ... checking environment variables ...
> > >    
> > >    ########################################################
> > >    make_installer.pl, version 1.0
> > >    Product list file: openoffice.lst
> > >    Taking setup script from solver
> > >    Unpackpath:
> /tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util
> > >    Compiler: unxlngi6
> > >    Product: OpenOffice
> > >    BuildID: 9011
> > >    Build: OOB680
> > >    No minor set
> > >    Product version
> > >    Installpath: /usr/lib/openoffice
> > >    Package format: native
> > >    Package list file: ../inc_openoffice/unix/packagelist.txt
> > >    Addon-Package list file: ../inc_openoffice/unix/packagelist_language.txt
> > >    Not 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
> > >    ...... searching unzip ...
> > >            Found: /usr/bin/unzip
> > >    ... analyzing openoffice.lst ...
> > >    ... analyzing script:
>
/tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/setup_osl.ins
> ...
> > >    ... analyzing directories ...
> > >    ... analyzing files ...
> > >    ... analyzing scpactions ...
> > >    ... analyzing shortcuts ...
> > >    ... analyzing profile ...
> > >    ... analyzing profileitems ...
> > >    ... analyzing modules ...
> > >    ------------------------------------
> > >    ... languages en-US ...
> > >    ... analyzing files ...
> > >    ... analyzing files with flag ARCHIVE ...
> > >    ... analyzing files with flag SCPZIP_REPLACE ...
> > >    ... analyzing files with flag PATCH_SO_NAME ...
> > >    ... creating preregistered services.rdb ...
> > >    
> > >    **************************************************
> > >    ERROR: ERROR: Could not register all components!
> > >    in function: create_services_rdb
> > >    **************************************************
> > >    
> > >    **************************************************
> > >    ERROR: Saved logfile:
>
/tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//logging/en-US/log_OOB680__en-US.log
> > >    **************************************************
> > >    ... cleaning the output tree ...
> > >    ... removing directory
>
/tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//zip/en-US
> ...
> > >    ... removing directory
>
/tmp/portage/openoffice-2.0.2-r1/work/ooo-build-2.0.2.9/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//services.rdb/en-US_witherror_1
> ...
> > >    Thu May 25 02:36:02 2006 (00:36 min.)
> > >    Failed to install: Bad file descriptor at ./ooinstall line 129.
> > >    make: *** [install] Error 1
> > > 
> > >  
> > >  What did I so badly wrong here ?
> > > 
> > >  Kind regards,
> > >  mcc
> > > 
> > >  PS: I symlinked /var/tmp/portags to /tmp/portage (I carefully copied
> > >  all permissions settings...) due to space problems.
> > > 
> > >  
> > -- 
> > gentoo-user@gentoo.org mailing list
> > 
> -- 
> gentoo-user@gentoo.org mailing list
> 
> 

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Teresa and Dale]

Richard Broersma Jr wrote:

>I was having problems getting OO to build.  I issued the following bug report. 
>http://bugs.gentoo.org/show_bug.cgi?id=126937
>
>In my case the it was due to a hardware issue.  I kept retrying the emerge and at last it
>succeeded (on a very very cold evening...).  My best guess is that the large volume of builds was
>causing my CPU to over heat.  This guess was bolster by the fact that I am able to get consistent
>successful builds of OO when I pull of the computer's case and direct a cooling fan on the
>computers internals. :-)
>
>I realize my "fix/work around" might not sit well with most people.  But in my defense, it is just
>a toy computer that I have fun tinkering around with.
>
>--- Meino Christian Cramer <Meino.Cramer@gmx.de> wrote:
>
>  
>

If you want to test the cooling system, compile OOo or kde-meta.  That
will bring out all the heat bugs for sure.  Unless you run folding like
me.  That will do it too.

Dale
:-)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Teresa and Dale]

Meino Christian Cramer wrote:

>From: Jeff <jmg_071769@comcast.net>
>Subject: Re: [gentoo-user] OpenOffice build failed.
>Date: Thu, 25 May 2006 00:17:27 -0400
>
>  
>
>>Good Lord man... why would you want to compile OO from source?
>>    
>>
>
> Since gentoo offers this...
>
> Or in other words:
> Why does gentoo offer it, if one needs to be god to get it run ???
> :)
>
>
>  
>

I compile mine from source too.  If I wanted binary ones I would use
Mandrake, Mandriva or whatever it is called this week.  Never had that
error before though.

Dale
:-)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 491 bytes --]

On Thu, 25 May 2006 00:17:27 -0400, Jeff wrote:

> Good Lord man... why would you want to compile OO from source?
> 
> emerge openoffice-bin

Maybe because he is using an architecture for which the bin package is
not available? It takes around 16 hours to compile 2.0.2 on my laptop.
but it's better than using 1.1.2.


-- 
Neil Bothwick

The present never ages. Each moment is like a snowflake, unique,
unspoiled, unrepeatable, and can be appreciated in its surprisingness.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] OpenOffice build failed.

[Matthias Langer]

<snip>
> >  PS: I symlinked /var/tmp/portags to /tmp/portage (I carefully copied
> >  all permissions settings...) due to space problems.
</snip>
I've not noticed this before:
Neil Botwick once wrote to me here, in gentoo-user:
<quote>
If you want to move directories, avoid wholesale symlinking like this as
it always ends in tears ...
</quote>
You may take a look at:
http://news.gmane.org/find-root.php?message_id=%3c434666D9.3070306%
40gmx.at%3e

Maybe you want to solve this issue before rebuilding your system (i
would do that in either case).

Regards,
Matthias


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]

On Thu, 25 May 2006 04:50:41 +0200 (CEST), Meino Christian Cramer wrote:

>  I tried to build OpenOffice from source. After hours of copmiling it
>  fails with:
>    
>    **************************************************
>    ERROR: ERROR: Could not register all components!
>    in function: create_services_rdb
>    **************************************************
This looks like the error I was getting, see
http://bugs.gentoo.org/show_bug.cgi?id=126587. The solution was twofold,
first re-emerge the latest hunspell, then emerge openoffice-2.0.2-r2 (not
the r1 you are trying).

>  PS: I symlinked /var/tmp/portags to /tmp/portage (I carefully copied
>  all permissions settings...) due to space problems.

That's a bit kludgy. Why not set PORTAGE_TMPDIR to a suitable directory,
either in make.conf or when running the emerge.


-- 
Neil Bothwick

Don't forget that MS-Windows is just a temporary workaround until you can
switch to a GNU system.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] OpenOffice build failed.

[Kenton Groombridge]

Meino Christian Cramer wrote:
> Hi,
>
>  I tried to build OpenOffice from source. After hours of copmiling it
>  fails with:
>  
>  What did I so badly wrong here ?
>
>  Kind regards,
>  mcc
>   
I have the same problem, looks to be same bug posted in:

http://bugs.gentoo.org/show_bug.cgi?id=126777

and

http://bugs.gentoo.org/show_bug.cgi?id=126587

Ken
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Meino Christian Cramer]

From: Kenton Groombridge <kgroombr@charter.net>
Subject: Re: [gentoo-user] OpenOffice build failed.
Date: Thu, 25 May 2006 17:16:51 -

Hi,

As suggested I tried to install the newest hunspell available and
installed openoffice-2.0.2-r2.

The build failed again with the same error while installing.

This time I simultaneously run a script, which logs the CPU core
temperature into a logfile every ten seconds.

The highest temperature logged was 44.5 degree celsius.

Any other ways to install OO from source successfully ?

Somehow frustrated,
Meino
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Richard Fish]

On 5/28/06, Meino Christian Cramer <Meino.Cramer@gmx.de> wrote:
> From: Kenton Groombridge <kgroombr@charter.net>
> Subject: Re: [gentoo-user] OpenOffice build failed.
> Date: Thu, 25 May 2006 17:16:51 -
>
> Hi,
>
> As suggested I tried to install the newest hunspell available and
> installed openoffice-2.0.2-r2.
>
> The build failed again with the same error while installing.

What does the openoffice logfile mentioned in the error message
contain?  Also, could you post the output of emerge --info?

> This time I simultaneously run a script, which logs the CPU core
> temperature into a logfile every ten seconds.

You might also do the same with 'df'.  Building OOo requires an insane
amount of disk space...

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Philip Webb]

060528 Richard Fish wrote:
> On 5/28/06, Meino Christian Cramer <Meino.Cramer@gmx.de> wrote:
> You might also do the same with 'df'.
> Building OOo requires an insane amount of disk space...

 2.0.2  needed  4 GB  on my machine: make sure PORTAGE_TMPDIR is big enough.
I have a big  13 GB  partition which I call '/z' for making ISOs etc
& use  /z/tmp  as PORTAGE_TMPDIR .

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : purslow@chass.utoronto.ca
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Meino Christian Cramer]

From: "Richard Fish" <bigfish@asmallpond.org>
Subject: Re: [gentoo-user] OpenOffice build failed.
Date: Sun, 28 May 2006 22:17:32 -0700

> On 5/28/06, Meino Christian Cramer <Meino.Cramer@gmx.de> wrote:
> > From: Kenton Groombridge <kgroombr@charter.net>
> > Subject: Re: [gentoo-user] OpenOffice build failed.
> > Date: Thu, 25 May 2006 17:16:51 -
> >
> > Hi,
> >
> > As suggested I tried to install the newest hunspell available and
> > installed openoffice-2.0.2-r2.
> >
> > The build failed again with the same error while installing.
> 
> What does the openoffice logfile mentioned in the error message
> contain?  Also, could you post the output of emerge --info?

  Hopefully I have undertsood, what you are asking for (I am still
  exploring the wonderful world of gentoo and English isn't my
  mother's tongue...)

  So:

  The compile process (a full very long log of all output is on my
  disk -- if you want it I can send you a compressed version...)
  stopped with this message:

     Package list file: ../inc_openoffice/unix/packagelist.txt
     Addon-Package list file: ../inc_openoffice/unix/packagelist_language.txt
     Not 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
     ...... searching unzip ...
             Found: /usr/bin/unzip
     ... analyzing openoffice.lst ...
     ... analyzing script: /tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.11/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/setup_osl.ins ...
     ... analyzing files ...
     ... analyzing scpactions ...
     ... analyzing shortcuts ...
     ... analyzing profile ...
     ... analyzing profileitems ...
     ... analyzing modules ...
     ------------------------------------
     ... languages en-US ...
     ... analyzing files ...
     ... analyzing files with flag ARCHIVE ...
     ... analyzing files with flag SCPZIP_REPLACE ...
     ... analyzing files with flag PATCH_SO_NAME ...
     ... creating preregistered services.rdb ...
     
     **************************************************
     ERROR: ERROR: Could not register all components!
     in function: create_services_rdb
     **************************************************
     
     **************************************************
     ERROR: Saved logfile: /tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.11/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//logging/en-US/log_OOB680__en-US.logcleaning the output tree ...
     ... removing directory /tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.11/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//zip/en-US ...o-build-2.0.2.11/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//services.rdb/en-US_witherror_1 ...ed to install: Bad file descriptor at ./ooinstall line 129.
     make: *** [install] Error 1

 Seems to me the same report as mailed previuosly...

   emerge --info says:
   
     solfire:/root>emerge --info
     Portage 2.0.54-r2 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r3, 2.6.16.18 i686)
     =================================================================
     System uname: 2.6.16.18 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
     Gentoo Base System version 1.6.14
     dev-lang/python:     2.4.2
     dev-python/pycrypto: 2.0.1-r5
     dev-util/ccache:     [Not Present]
     dev-util/confcache:  [Not Present]
     sys-apps/sandbox:    1.2.17
     sys-devel/autoconf:  2.13, 2.59-r7
     sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
     sys-devel/binutils:  2.16.1-r2
     sys-devel/libtool:   1.5.22
     virtual/os-headers:  2.6.11-r2
     ACCEPT_KEYWORDS="x86"
     AUTOCLEAN="yes"
     CBUILD="i386-pc-linux-gnu"
     CFLAGS="-O3 -m3dnow -march=athlon-xp -mtune=athlon64 -msse -msse2 -msse3 -m3dnow -mfpmath=sse -funroll-loops -fomit-frame-pointer -fforce-mem -fforce-addr -finline-functions -falign-functions=4 -mpreferred-stack-boundary=2"
     CHOST="i386-pc-linux-gnu"
     CONFIG_PROTECT="/etc /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/lib/X11/xkb /usr/share/config"
     CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
     CXXFLAGS="-O3 -m3dnow -march=athlon-xp -mtune=athlon64 -msse -msse2 -msse3 -m3dnow -mfpmath=sse -funroll-loops -fomit-frame-pointer -fforce-mem -fforce-addr -finline-functions -falign-functions=4 -mpreferred-stack-boundary=2"
     DISTDIR="/usr/portage/distfiles"
     FEATURES="autoconfig distlocks sandbox sfperms strict"
     GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo "
     MAKEOPTS="-j 4"
     PKGDIR="/usr/portage/packages"
     PORTAGE_TMPDIR="/var/tmp"
     PORTDIR="/usr/portage"
     SYNC="rsync://rsync.gentoo.org/gentoo-portage"
     USE="x86 X acl alsa apache2 apm arts audiofile avi berkdb bitmap-fonts bonobo bzip2 cdr cli crypt cscope cups curl dri dts eds emboss encode esd ethereal exif expat fam flac foomaticdb fortran gd gdbm gif glut gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml guile idn imagemagick imlib ipv6 isdnlog jack java jpeg kde lcms libg++ libwww mad mikmod mng motif mp3 mpeg ncurses nls nptl ogg openal opengl oss pam pcre pdflib perl plotutils png pppd python qt quicktime readline recode reflection scanner sdl session slang speex spell spl sqlite ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts udev usb vorbis xine xml xml2 xmms xorg xv xvid zlib video_cards_radeon userland_GNU kernel_linux elibc_glibc"
     Unset:  CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS, PORTAGE_RSYNC_OPTS, PORTDIR_OVERLAY

 BUT: 
 I updated binutils and gcc afterwards to that version reported by
 this command.


 I dont know exactly, what you mean with "openoffice logfile"...but
 the file located normally in /var/tmp/portage (/tmp/portage/ in my case) are
 still there. If you point me directly to the specific file, I will be
 happy to mail it to you / the list.

> > This time I simultaneously run a script, which logs the CPU core
> > temperature into a logfile every ten seconds.
> 
> You might also do the same with 'df'.  Building OOo requires an insane
> amount of disk space...

  There were about 9 GByte free on /tmp/portage before I started the
  compile process.

> -Richard
> 
> -- 
> gentoo-user@gentoo.org mailing list
> 

 Meino

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Richard Fish]

On 5/29/06, Meino Christian Cramer <Meino.Cramer@gmx.de> wrote:
> Before I will restart the whole thing again I would be happy if you
> could take a look on the logfile. I have attached it to this mail,

Here is the error:

Systemcall:  /tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.11/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/regcomp
-register -br /tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.11/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/types.rdb
-br /tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.11/build/OOO_2_0_2/solver/680/unxlngi6.pro/bin/pyuno_services.rdb
-r /tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.11/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//services.rdb/en-US_inprogress_1/services.rdb
-c vnd.openoffice.pymodule:mailmerge -l com.sun.star.loader.Python
2>&1 |
'import site' failed; use -v for traceback
register component 'vnd.openoffice.pymodule:mailmerge' in registry
'/tmp/portage/openoffice-2.0.2-r2/work/ooo-build-2.0.2.11/build/OOO_2_0_2/instsetoo_native/util/OpenOffice//services.rdb/en-US_inprogress_1/services.rdb'
failed!
error (RuntimeException): python-loader:exceptions.ImportError: No
module named os, traceback follows
Coludn't import traceback module

It looks like openoffice doesn't like the python that is on your
system.  But I don't understand why, because the os, site, and
traceback modules are a part of python, and really must exist.  In
fact portage relies on python, so if python were really broken portage
would not work.

So I guess now we should take a look at the output of:

eix dev-lang/python  (you may need to merge eix for this)
emerge -pv dev-lang/python
env | grep PYTHON
python -c "import sys ; print sys.path"

I suppose you can also try running the command shown on the
Systemcall: line and see if the problem repeats itself...

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Matthias Langer]

<snip>
>      CFLAGS="-O3 -m3dnow -march=athlon-xp -mtune=athlon64 -msse -msse2 -msse3 -m3dnow -mfpmath=sse -funroll-loops -fomit-frame-pointer  -finline-functions -falign-functions=4 -mpreferred-stack-boundary=2"
<snip>

Before doing anything else, please clean up your CFLAGS and do 
"# emerge -e system; emerge -e world"

If you realy want x86 (with your cpu i would reinstall an amd64 system
http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml) then use:

CFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer"

because, mostly all of your flags are redundant and the combination
"-march=athlon-xp -mtune=athlon64" will give you nothing but maybe
broken compiler output.

You may also be interested in these pages:
http://gentoo-wiki.com/Safe_Cflags
http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/Optimize-Options.html#Optimize-Options
http://gentoo-wiki.com/CFLAGS
http://gentoo-wiki.com/CFLAGS_matrix

HTH,
Matthias




-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Meino Christian Cramer]

From: Matthias Langer <mlangc@gmx.at>
Subject: Re: [gentoo-user] OpenOffice build failed.
Date: Mon, 29 May 2006 21:14:25 +0200

> <snip>
> >      CFLAGS="-O3 -m3dnow -march=athlon-xp -mtune=athlon64 -msse -msse2 -msse3 -m3dnow -mfpmath=sse -funroll-loops -fomit-frame-pointer  -finline-functions -falign-functions=4 -mpreferred-stack-boundary=2"
> <snip>
> 
> Before doing anything else, please clean up your CFLAGS and do 
> "# emerge -e system; emerge -e world"
> 
> If you realy want x86 (with your cpu i would reinstall an amd64 system
> http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml) then use:
> 
> CFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer"
> 
> because, mostly all of your flags are redundant and the combination
> "-march=athlon-xp -mtune=athlon64" will give you nothing but maybe
> broken compiler output.
> 
> You may also be interested in these pages:
> http://gentoo-wiki.com/Safe_Cflags
> http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/Optimize-Options.html#Optimize-Options
> http://gentoo-wiki.com/CFLAGS
> http://gentoo-wiki.com/CFLAGS_matrix
> 
> HTH,
> Matthias
> 
> 
> 
> 
> -- 
> gentoo-user@gentoo.org mailing list
> 

My decision against 64 bit and pro 32 was done, cause 64 bit gives me
a performance gain only in some special cirumstances (beside only a
few others:  when rendering with 64 Bit aware Raytracers) but gives me
for sure trouble with software, which isn't 64Bit-ready (according to
different articles of the german c't computer magazine (Heise press).

When changing CFLAGs on half the way...do I have to recompile my whole
system? And -- only from the logical point of view -- redundancy may
be not a sign of cleverness not a sign of cleverness but it does not
hurt does not hurt the overall context since it instructs the compiler
twice to do the same?!

Bad compiler output is another thing. 

Keep hacking!
mcc
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Matthias Langer]

On Mon, 2006-05-29 at 21:31 +0200, Meino Christian Cramer wrote:
> From: Matthias Langer <mlangc@gmx.at>
> Subject: Re: [gentoo-user] OpenOffice build failed.
> Date: Mon, 29 May 2006 21:14:25 +0200
> 
> > <snip>
> > >      CFLAGS="-O3 -m3dnow -march=athlon-xp -mtune=athlon64 -msse -msse2 -msse3 -m3dnow -mfpmath=sse -funroll-loops -fomit-frame-pointer  -finline-functions -falign-functions=4 -mpreferred-stack-boundary=2"
> > <snip>
> > 
> > Before doing anything else, please clean up your CFLAGS and do 
> > "# emerge -e system; emerge -e world"
> > 
> > If you realy want x86 (with your cpu i would reinstall an amd64 system
> > http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml) then use:
> > 
> > CFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer"
> > 
> > because, mostly all of your flags are redundant and the combination
> > "-march=athlon-xp -mtune=athlon64" will give you nothing but maybe
> > broken compiler output.
> > 
> > You may also be interested in these pages:
> > http://gentoo-wiki.com/Safe_Cflags
> > http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/Optimize-Options.html#Optimize-Options
> > http://gentoo-wiki.com/CFLAGS
> > http://gentoo-wiki.com/CFLAGS_matrix
> > 
> > HTH,
> > Matthias
> > 
> > 
> > 
> > 
> > -- 
> > gentoo-user@gentoo.org mailing list
> > 
> 
> My decision against 64 bit and pro 32 was done, cause 64 bit gives me
> a performance gain only in some special cirumstances (beside only a
> few others:  when rendering with 64 Bit aware Raytracers) but gives me
> for sure trouble with software, which isn't 64Bit-ready (according to
> different articles of the german c't computer magazine (Heise press).
> 
> When changing CFLAGs on half the way...do I have to recompile my whole
> system? And -- only from the logical point of view -- redundancy may
> be not a sign of cleverness not a sign of cleverness but it does not
> hurt does not hurt the overall context since it instructs the compiler
> twice to do the same?!
> 
> Bad compiler output is another thing. 
> 
> Keep hacking!
> mcc

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Matthias Langer]

On Mon, 2006-05-29 at 21:31 +0200, Meino Christian Cramer wrote:
> From: Matthias Langer <mlangc@gmx.at>
> Subject: Re: [gentoo-user] OpenOffice build failed.
> Date: Mon, 29 May 2006 21:14:25 +0200
> 
> > <snip>
> > >      CFLAGS="-O3 -m3dnow -march=athlon-xp -mtune=athlon64 -msse -msse2 -msse3 -m3dnow -mfpmath=sse -funroll-loops -fomit-frame-pointer  -finline-functions -falign-functions=4 -mpreferred-stack-boundary=2"
> > <snip>
> > 
> > Before doing anything else, please clean up your CFLAGS and do 
> > "# emerge -e system; emerge -e world"
> > 
> > If you realy want x86 (with your cpu i would reinstall an amd64 system
> > http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml) then use:
> > 
> > CFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer"
> > 
> > because, mostly all of your flags are redundant and the combination
> > "-march=athlon-xp -mtune=athlon64" will give you nothing but maybe
> > broken compiler output.
> > 
> > You may also be interested in these pages:
> > http://gentoo-wiki.com/Safe_Cflags
> > http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/Optimize-Options.html#Optimize-Options
> > http://gentoo-wiki.com/CFLAGS
> > http://gentoo-wiki.com/CFLAGS_matrix
> > 
> > HTH,
> > Matthias
> > 
> > 
> > 
> > 
> > -- 
> > gentoo-user@gentoo.org mailing list
> > 
> 
> My decision against 64 bit and pro 32 was done, cause 64 bit gives me
> a performance gain only in some special cirumstances (beside only a
> few others:  when rendering with 64 Bit aware Raytracers) but gives me
> for sure trouble with software, which isn't 64Bit-ready (according to
> different articles of the german c't computer magazine (Heise press).
> 
> When changing CFLAGs on half the way...do I have to recompile my whole
> system? And -- only from the logical point of view -- redundancy may
> be not a sign of cleverness not a sign of cleverness but it does not
> hurt does not hurt the overall context since it instructs the compiler
> twice to do the same?!
> 

Of course, redunant compiler options should not do any harm but:
1.) they are difficult to read for people that may help you.
2.) -O3 turns on a group of compiler switches that are veryfied by
    by the gcc devs to produce good results. The group of these
    switches may change from time to time. Without further invention,
    your custum, today redunant swiches, may break your system 
    tomorrow, after you have choosen to do a compiler upgrade and the
    the actual contents of -O3 have changed. The same applies of course
    to march=athlon-xp. One (harmless) example where this applies is 
    '-fforce-mem'. This option will be completly removed with gcc-4.2,
    does nothing with gcc-4.1, but is activated with '-O3' for
    gcc-3.4.x.

More generally: After doing some experiments, i've decided to use
CFLAGS="-march=athlon-xp -O2 -pipe". I don't think that my system would
be noticeably faster with -O3, as -O3 often gains you nothing.
'-fomit-frame-pointer' may give you a few percent, but it may interfere
with debuging. 

>From the gentoo-x86-handbook:
Mind you that using -fomit-frame-pointer (which doesn't keep the frame
pointer in a register for functions that don't need one) might have
serious repercussions on the debugging of applications!

>From the gcc-manual:
-O also turns on -fomit-frame-pointer on machines where doing so does
not interfere with debugging

Besides, by looking at the terminal while merging packages, you will
soon notice, that lot's of packages add their very own CFLAGS to your
default ones. For example mplayer or xine-lib was compiled with '-O3' on
my system, allthough i have '-O2' in my CFLAGS. (As far as i know, "gcc
-O3 -O2" == "gcc -O3").

> Bad compiler output is another thing.

In this exactly is the reason, i told you to better rebuild your whole
system:
1.) emerge -e system so that all base packages (especially gcc, 
    libtool,  glibc, !python!, ...) are ok.
2.) emerge -e world so that all your packages are rebuild with your 
    fixed toolchain.

If you still problems with openoffice afterwards, it is sure that 
they are not related to your CFLAGS. Only then it makes sense to me to
look at this problem more in detail.

Have a nice day,
Matthias

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Christian Limberg]

> Besides, by looking at the terminal while merging packages, you will
> soon notice, that lot's of packages add their very own CFLAGS to your
> default ones. For example mplayer or xine-lib was compiled with '-O3' on
> my system, allthough i have '-O2' in my CFLAGS. (As far as i know, "gcc
> -O3 -O2" == "gcc -O3").
> 

Hi,

the compiler takes the later options you specify, if they together makes 
no sense.

So gcc -O2 -O3 bla.c is the same as gcc -O3 bla.c

and gcc -O3 -O2 bla.c is the same as gcc -O2 bla.c.

Regards Christian
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Graham Murray]

Matthias Langer <mlangc@gmx.at> writes:

> Besides, by looking at the terminal while merging packages, you will
> soon notice, that lot's of packages add their very own CFLAGS to your
> default ones. For example mplayer or xine-lib was compiled with '-O3' on
> my system, allthough i have '-O2' in my CFLAGS. (As far as i know, "gcc
> -O3 -O2" == "gcc -O3").

Where packages do this, should they not filter out the appropriate
flags from the user's CFLAGS and substitute their flags rather than
having both flags on the command line?
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice build failed.

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]

Tuesday 30 May 2006 07:41 skrev Graham Murray:
> > Besides, by looking at the terminal while merging packages, you will
> > soon notice, that lot's of packages add their very own CFLAGS to your
> > default ones. For example mplayer or xine-lib was compiled with '-O3' on
> > my system, allthough i have '-O2' in my CFLAGS. (As far as i know, "gcc
> > -O3 -O2" == "gcc -O3").
>
> Where packages do this, should they not filter out the appropriate
> flags from the user's CFLAGS and substitute their flags rather than
> having both flags on the command line?

Not in this particular case. xine-lib is a good example. src_compile() 
contains the following in the ebuild (and more):

if [[ $(tc-arch) == "x86" ]]; then
	filter-flags -fforce-addr
	filter-flags -momit-leaf-frame-pointer
	is-flag -O? || append-flags -O2
fi

On an x86 architecture it filters out -fforce-addr 
and -momit-leaf-frame-pointer. If the CFLAGS contain any optimizations it 
just appends -O2 yielding that -O2 will be used as stated by Christian 
Limberg. In 'man gcc' you find the following statement:

"If you use multiple -O options, with or without level numbers, the last such 
option is the one that is effective."

So this is completely legal.

And I very much doubt that there are any ebuilds in the portage tree that 
enforces -O3 or higher...

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] OpenOffice build failed.

[Matthias Langer]

On Tue, 2006-05-30 at 08:04 +0200, Bo Ørsted Andresen wrote:
> Tuesday 30 May 2006 07:41 skrev Graham Murray:
> > > Besides, by looking at the terminal while merging packages, you will
> > > soon notice, that lot's of packages add their very own CFLAGS to your
> > > default ones. For example mplayer or xine-lib was compiled with '-O3' on
> > > my system, allthough i have '-O2' in my CFLAGS. (As far as i know, "gcc
> > > -O3 -O2" == "gcc -O3").
> >
> > Where packages do this, should they not filter out the appropriate
> > flags from the user's CFLAGS and substitute their flags rather than
> > having both flags on the command line?
> 
> Not in this particular case. xine-lib is a good example. src_compile() 
> contains the following in the ebuild (and more):
> 
> if [[ $(tc-arch) == "x86" ]]; then
> 	filter-flags -fforce-addr
> 	filter-flags -momit-leaf-frame-pointer
> 	is-flag -O? || append-flags -O2
> fi
> 
> On an x86 architecture it filters out -fforce-addr 
> and -momit-leaf-frame-pointer. If the CFLAGS contain any optimizations it 
> just appends -O2 yielding that -O2 will be used as stated by Christian 
> Limberg. In 'man gcc' you find the following statement:
> 
> "If you use multiple -O options, with or without level numbers, the last such 
> option is the one that is effective."
> 
> So this is completely legal.
> 
> And I very much doubt that there are any ebuilds in the portage tree that 
> enforces -O3 or higher...
> 
Well, you are right: However, what i said still applies: Lot's of
packages add their very own CFLAGS (-fomit-frame-pointer,
-ffunction-sections are two examples for xine-lib).

Matthias

-- 
gentoo-user@gentoo.org mailing list