Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 7004 - building openoffice fails (reopened)
Summary: building openoffice fails (reopened)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Seth Chandler
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-25 05:53 UTC by Jan Schubert
Modified: 2003-02-04 19:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Schubert 2002-08-25 05:53:36 UTC
# emerge openoffice  
Calculating dependencies ...done!  
>>> emerge app-office/openoffice-1.0.0-r2 to /  
>>> md5 ;-) OOo_1.0.0_source.tar.bz2  
>>> md5 ;-) gpc231.tar.Z  
>>> md5 ;-) openoffice-1.0.0b-registry.tbz2  
 *  
 * This ebuild has only been tested with the blackdown port of  
 * java.  If you use another java implementation, it could fail  
 * horribly, so please merge the blackdown-jdk and set it as  
 * system VM before proceeding:  
 *  
 *  # emerge blackdown-jdk  
 *  # java-config --set-system-vm=blackdown-jdk-1.3.1  
 *  # env-update  
 *  # source /etc/profile  
 *  
 * At the time of writing, this was version 1.3.1, so please  
 * adjust the version according to the version installed in  
 * /opt.  
 *  
 * If you however want to test another JDK (not officially supported),  
 * you could do the following:  
 *  
 *  # export FORCE_JAVA=yes  
 *  
  
!!! ERROR: The ebuild did not complete successfully.  
!!! Function pkg_setup, Line 297, Exitcode 0  
!!! (no error message)  
  
!!! emerge aborting on   
/usr/portage/app-office/openoffice/openoffice-1.0.0-r2.ebuild .
Comment 1 Jan Schubert 2002-08-25 08:10:07 UTC
after doing a 
 
# java-config --set-system-vm=blackdown-jdk-1.3.1 
# env-update 
 
the build starts. Sorry, for not reading the error-msg. 
Comment 2 Jan Schubert 2002-08-25 08:16:58 UTC
Is there any issue using gcc32 building OO? Now, i get the following error: 
 
---- 
 
checking for awk... /bin/awk 
checking for sed... /bin/sed 
checking the operating system... checked (Linux) 
checking for gcc... gcc 
checking whether the C compiler (gcc -march=pentium4 -O4 -pipe ) works... yes 
checking whether the C compiler (gcc -march=pentium4 -O4 -pipe ) is a 
cross-compiler... no 
checking whether we are using GNU C... yes 
checking whether gcc accepts -g... yes 
checking for gcc... (cached) gcc 
checking whether the C compiler (gcc -march=pentium4 -O4 -pipe ) works... yes 
checking whether the C compiler (gcc -march=pentium4 -O4 -pipe ) is a 
cross-compiler... no 
checking whether we are using GNU C... (cached) yes 
checking whether gcc accepts -g... (cached) yes 
checking the GNU gcc compiler version... configure: error: found version gcc 
(GCC) 3.2 Copyright (C) 2002 Free Software Foundation, Inc. This is free 
software; see the source for copying conditions. There is NO warranty; not even 
for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE., but use of gcc 3.x 
requested 
 
!!! ERROR: The ebuild did not complete successfully. 
!!! Function src_compile, Line 59, Exitcode 1 
!!! (no error message) 
 
 ...done! 
>>> emerge app-office/openoffice-1.0.0-r2 to / 
>>> md5 ;-) OOo_1.0.0_source.tar.bz2 
>>> md5 ;-) gpc231.tar.Z 
>>> md5 ;-) openoffice-1.0.0b-registry.tbz2 
!!! emerge aborting on  
/usr/portage/app-office/openoffice/openoffice-1.0.0-r2.ebuild . 
Comment 3 Chris Snyder 2002-09-03 01:07:15 UTC
This appears to be due to the fact that running gcc --version with versions
prior to 3.2 would give you the version number only, while 3.2 returns copyright
info as well.  Sounds like some sed'ing of the OO configuration script is in order.