Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 120105 - openoffice-2.0.1 wont compile through "ebuild openoffice compile" with use-flag java enabled
Summary: openoffice-2.0.1 wont compile through "ebuild openoffice compile" with use-fl...
Status: VERIFIED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: Low normal (vote)
Assignee: Gentoo Office Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-23 14:40 UTC by Philipp Reinkemeier
Modified: 2006-01-26 06:52 UTC (History)
2 users (show)

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 Philipp Reinkemeier 2006-01-23 14:40:17 UTC
Portage 2.0.54 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.15-gentoo-r1 i686)
=================================================================
System uname: 2.6.15-gentoo-r1 i686 Mobile Intel(R) Pentium(R) 4     CPU 2.80GHz
Gentoo Base System version 1.6.14
dev-lang/python:     2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
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
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="x86 X acpi alsa apm asf audiofile avi berkdb bitmap-fonts bzip2 cdr cdrw crypt cups curl dvd dvdr emboss encode ethereal exif expat fam ffmpeg foomaticdb gdbm gif glut gmp gpm gstreamer gtk gtk2 idn imagemagick imlib ipv6 jpeg lcms libg++ libwww lua mad mikmod mmx mng motif mp3 mpeg ncurses network nls nptl nptlonly ogg oggvorbis openal opengl oss pam pcre pdflib perl png ppds python qt quicktime readline sdl spell sse sse2 ssl svga tcpd tetex tiff truetype truetype-fonts type1-fonts udev usb vorbis win32codecs xine xml2 xmms xv xvid zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS


- Java use-flag is explicitly set in /etc/portage/packages.use for openoffice

- I have sun-jdk-1.4.2.10-r2 installed and sun-jdk-1.50.06-r2. Java 1.4 is my system's default vm, but anyway the other vm doesn't work either.

- I tried to update openoffice from 2.0.0 to 2.0.1
These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild     U ] app-office/openoffice-2.0.1 [2.0.0] -binfilter +curl -eds -gnome +gtk +java -kde -ldap -mozilla +xml2 +zlib 0 kB 

Total size of downloads: 0 kB

- It gives me the following error:

.
.
.
.
Env for configure ends
********************************************************************
*                                                                  *
*   OpenOffice.org build configuration.                            *
*                                                                  *
*   The configure proces checks your platform to see whether       *
*   you can build OpenOffice.org on it.                            *
*   This proces checks all pre-requisites and generates a file     *
*   containing the necessary environment variables.                *
*   Source this file after configure has ended successfully.       *
*                                                                  *
*   Any warning that is generated during the configure process     *
*   must be taken into account, since it can be a reason for       *
*   an unsuccessful build of OpenOffice.org                        *
*                                                                  *
********************************************************************

********************************************************************
*                                                                  *
*   Checking the platform pre-requisites.                          *
*                                                                  *
********************************************************************

checking for gawk... gawk
checking for gawk... /bin/gawk
checking for sed... /bin/sed
checking for solenv environment... default
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking whether to enable crashdump feature... no
checking whether to do a debug build... no
checking whether to build with additional debug utilities... no, full product build
checking whether to include symbols into final build... no
checking whether to enable native CUPS support... yes
checking whether to enable fontconfig support... yes
checking whether to enable filters for legacy binary file formats (StarOffice 5.2)... no
checking whether to enable the Access import pieces... no
checking whether to use RPATH in shared libraries... yes
checking whether to include MySpell dictionaries... no
checking which shell to use... tcsh
checking for tcsh... /bin/tcsh
checking gcc home... /usr
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for gcc... /usr/bin/gcc
checking the GNU gcc compiler version... checked (gcc 3.4.4)
checking for -Bdirect linker support ... not found 
checking for GNU make... make
checking the GNU make version... make 3.80
checking whether to enable Mono bindings... no
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking whether to disable vba feature... no
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking cups/cups.h usability... yes
checking cups/cups.h presence... yes
checking for cups/cups.h... yes
checking security/pam_appl.h usability... yes
checking security/pam_appl.h presence... yes
checking for security/pam_appl.h... yes
checking whether to link to libpam... no, dynamically open it
checking whether to link to libcrypt... yes
checking for crypt in -lcrypt... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking the GNU C++ compiler version... checked (g++ 3.4.4)
checking whether g++ has the enum bug... no
checking for g++ include path... /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/include/g++-v3
checking exception type... dwarf2
checking for STLport4 headers... using internal stlport.
checking whether to add custom build version... yes, Build 2.0.1.1
checking whether to build with Java support... yes
configure: error: /usr/lib/SunJava2-1.4.2/bin/java not found set with_jdk_home
make: *** [stamp/build] Error 1

!!! ERROR: app-office/openoffice-2.0.1 failed.
!!! Function src_compile, Line 217, Exitcode 2
!!! Build failed
!!! If you need support, post the topmost build error, NOT this status message.
Comment 1 Andreas Proschofsky (RETIRED) gentoo-dev 2006-01-23 22:37:51 UTC

*** This bug has been marked as a duplicate of 119577 ***
Comment 2 Philipp Reinkemeier 2006-01-24 01:22:30 UTC
Tested it again. It seems, that you can emerge it through command "emerge openoffice", but not through "ebuild /usr/portage/app-office/openoffice/openoffice-2.0.1.ebuild", which i used because i interrupted the emerge last night because of my noisy fan and continued it with the same command.

So finally with "ebuild" it interrupts, with "emerge" not!

May be, that there are some environment variables set in the ebuild, but outside the src_compile() function and therefore the "ebuild" command alone does not work.
Comment 3 Andreas Proschofsky (RETIRED) gentoo-dev 2006-01-24 06:32:07 UTC
(In reply to comment #2)
> 
> May be, that there are some environment variables set in the ebuild, but
> outside the src_compile() function and therefore the "ebuild" command alone
> does not work.
> 

Yes and that is perfectly fine.

Comment 4 Andreas Proschofsky (RETIRED) gentoo-dev 2006-01-24 06:37:21 UTC
Just to add to that: There are no relevant stuff vars set outside of src_compile() (only LINGUAS, but that doesn't count), anyway the problem seems to have been a messed up JAVA_HOME-var in your setup. But as it works when emerging the package properly, this is invalid
Comment 5 Thomas R. (TRauMa) 2006-01-24 17:16:10 UTC
I beg to differ, in src_unpack there is
	use amd64 && export DISTRO="Gentoo64" || export DISTRO="Gentoo"
but it really should be in pkg_setup. Since we don't go through src_unpack with the ebuild command, the gentoo specific config file isn't used at all (as we dont have a DISTRO env var). That's where that strange java path is coming from (no broken $JAVA_HOME).

>>the "ebuild" command alone
>> does not work.
>> 

>Yes and that is perfectly fine.

Sorry, but bollocks. Particulary for an ebuild that's blocking openoffice-bin, how do you propose switching from openoffice-bin to native without 8 hours office downtime without "ebuild compile"?
Anyway, if you just move this export where it belongs, ebuild compile works fine (fingers crossed, ask again in 8 hours if it really does...).
Comment 6 Thomas R. (TRauMa) 2006-01-24 17:18:25 UTC
Hm, sorry for flaming, it's late ;-). I missed comment #4 which puts comment #3 in perspective.
Comment 7 Andreas Proschofsky (RETIRED) gentoo-dev 2006-01-24 22:41:04 UTC
(In reply to comment #5)
> I beg to differ, in src_unpack there is
>         use amd64 && export DISTRO="Gentoo64" || export DISTRO="Gentoo"
> but it really should be in pkg_setup. Since we don't go through src_unpack with
> the ebuild command, the gentoo specific config file isn't used at all (as we
> dont have a DISTRO env var). That's where that strange java path is coming from
> (no broken $JAVA_HOME).

You are right and wrong. ;)

You are right that that this particular line belongs to src_compile (or pkg_setup), but you are wrong that this had anything to do with the original bug, otherwise the error message would have been totally different.

Anyway, I've moved it up now, thanks for noting this
Comment 8 Thomas R. (TRauMa) 2006-01-25 13:22:36 UTC
(In reply to comment #7)
> (In reply to comment #5)
> > Since we don't go through src_unpack with
> > the ebuild command, the gentoo specific config file isn't used at all (as we
> > dont have a DISTRO env var). That's where that strange java path is coming from
> > (no broken $JAVA_HOME).
> 
> You are right and wrong. ;)
> 
> You are right that that this particular line belongs to src_compile (or
> pkg_setup), but you are wrong that this had anything to do with the original
> bug, otherwise the error message would have been totally different.

No, I'm right and right. :-D. I had the same bug message as the original reporter, after starting the ebuild command with
DISTRO="Gentoo" ebuild foo compile
it worked. Thats because without the DISTRO env variable the Gentoo specific config file you create in the ebuild doesn't get used and so the OOo build system falls back to the default dir for java, which is /usr/lib/SunJava2-1.4.2/bin/java

Thats how I found the wrong line in the first place.

> Anyway, I've moved it up now, thanks for noting this
Thanks :-).
You or the reporter could move this bug from INVALID to CLOSED.
Comment 9 Philipp Reinkemeier 2006-01-26 06:52:44 UTC
(In reply to comment #8)
> I had the same bug message as the original
> reporter, after starting the ebuild command with
> DISTRO="Gentoo" ebuild foo compile
> it worked. Thats because without the DISTRO env variable the Gentoo specific
> config file you create in the ebuild doesn't get used and so the OOo build
> system falls back to the default dir for java, which is
> /usr/lib/SunJava2-1.4.2/bin/java
I think this is feasible.


Solution:
> > Anyway, I've moved it up now, thanks for noting this
> Thanks :-).
> You or the reporter could move this bug from INVALID to CLOSED.
>