/var/tmp/portage/openoffice-2.0.1/work/ooo-build-2.0.1.3/build/ooa680-m1/solenv/ bin/checkdll.sh -L../../../unxlngi6.pro/lib -L../lib -L/var/tmp/portage/openoffi ce-2.0.1/work/ooo-build-2.0.1.3/build/ooa680-m1/solenv/unxlngi6/lib -L/var/tmp/p ortage/openoffice-2.0.1/work/ooo-build-2.0.1.3/build/ooa680-m1/solver/680/unxlng i6.pro/lib -L/var/tmp/portage/openoffice-2.0.1/work/ooo-build-2.0.1.3/build/ooa6 80-m1/solenv/unxlngi6/lib -LNO_JAVA_HOME/lib -LNO_JAVA_HOME/jre/lib/i386 -LNO_JA VA_HOME/jre/lib/i386/client -LNO_JAVA_HOME/jre/lib/i386/native_threads -L/usr/li b ../../../unxlngi6.pro/lib/check_libflat680li.so Checking DLL ../../../unxlngi6.pro/lib/check_libflat680li.so ...: ok -rwxr-xr-x 1 root root 428360 Feb 22 13:11 ../../../unxlngi6.pro/lib/libflat680 li.so ------------------------------ Making: ../../../unxlngi6.pro/lib/iflat.lib no ImportLibs on Mac and *ix ------------- /var/tmp/portage/openoffice-2.0.1/work/ooo-build-2.0.1.3/build/ooa680-m1/connect ivity/source/drivers/hsqldb Not building jurt because Java is disabled /var/tmp/portage/openoffice-2.0.1/work/ooo-build-2.0.1.3/build/ooa680-m1/connect ivity/com/sun/star/sdbcx/comp/hsqldb ------------- /var/tmp/portage/openoffice-2.0.1/work/ooo-build-2.0.1.3/build/ooa680-m1/connect ivity/source/drivers/jdbc ------------- /var/tmp/portage/openoffice-2.0.1/work/ooo-build-2.0.1.3/build/ooa680-m1/connect ivity/source/drivers/kab KDE disabled - nothing to build /var/tmp/portage/openoffice-2.0.1/work/ooo-build-2.0.1.3/build/ooa680-m1/connect ivity/source/drivers/mdb Package glib-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `glib-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'glib-2.0' found dmake: Error code 1, while making 'Shell escape' ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-2.0.1/work/ ooo-build-2.0.1.3/build/ooa680-m1/connectivity/source/drivers/mdb make: *** [stamp/build] Error 1
Portage 2.0.54 (hardened/x86/2.6, gcc-3.4.4, glibc-2.3.5-r2, 2.6.14-hardened-r5 i686) ================================================================= System uname: 2.6.14-hardened-r5 i686 Intel(R) Pentium(R) 4 CPU 3.20GHz Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5, 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="-O2 -mtune=pentium4 -pipe -fomit-frame-pointer -ftracer -fforce-addr" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mtune=pentium4 -pipe -fomit-frame-pointer -ftracer -fforce-addr" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks nodoc noinfo noman sandbox sfperms strict" GENTOO_MIRRORS="http://mirror http://distfiles.gentoo.org" MAKEOPTS="-j3" PKGDIR="/usr/portage//packages/x86/" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage/" SYNC="rsync://mirror/gentoo-portage" USE="bzip2 crypt cups dlloader expat hardened jpeg ncurses openntpd pam pic png python readline ssl tcpd tiff truetype udev userlocales x86 xml2 zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Seemant, is this with a modified ebuild? Cause this is a build failure in a part of OOo which we are normally not building at all: the access-support (mdbtools). As we are not pulling in the necessary file, it is no surprise this fails.
(In reply to comment #2) > Seemant, is this with a modified ebuild? Cause this is a build failure in a > part of OOo which we are normally not building at all: the access-support > (mdbtools). As we are not pulling in the necessary file, it is no surprise this > fails. > Seemant? Need some comment here.
hi suka, I'm sorry for no response :( as far as I recall, this was a regular ebuild. I didn't change anything at all.
Nearly lost this bug. Seemant: Do you still get that?
Closing this, please reopen if you get this again, Seemant
*** Bug 160977 has been marked as a duplicate of this bug. ***
