Can't update openoffice with glsa-check.

Anything that pertains to Portage

Moderator: Moderators

Post Reply
smolloy
Simple Hen
Posts: 47
Joined: Wed May 02, 2007 5:24

Can't update openoffice with glsa-check.

Post by smolloy » Thu May 31, 2007 5:02

I'm having trouble updating openoffice with glsa-check. I get the following error message after less than an hour of compiling. I sync'ed emerge and ran "layman -S" before running "glsa-check -f all". Can anyone help?

Code: Select all

Making: ../../../unxlngx6.pro/slo/salsound2.obj
g++ -Wreturn-type -fmessage-length=0 -c -O2 -fno-strict-aliasing -Wuninitialized   -D_FILE_OFFSET_BITS=no -fvisibility=hidden -I/usr/include/startup-notification-1.0   -I.  -I../../../unxlngx6.pro/inc/salapp -I../inc -I../../../inc/pch -I../../../inc -I../../../unx/inc -I../../../unxlngx6.pro/inc -I. -I/var/tmp/portage/app-office/openoffice-2.1.0-r1/work/ooo/build/OOE680_m6/solver/680/unxlngx6.pro/inc/stl -I/var/tmp/portage/app-office/openoffice-2.1.0-r1/work/ooo/build/OOE680_m6/solver/680/unxlngx6.pro/inc/external -I/var/tmp/portage/app-office/openoffice-2.1.0-r1/work/ooo/build/OOE680_m6/solver/680/unxlngx6.pro/inc -I/var/tmp/portage/app-office/openoffice-2.1.0-r1/work/ooo/build/OOE680_m6/solenv/unxlngx6/inc -I/var/tmp/portage/app-office/openoffice-2.1.0-r1/work/ooo/build/OOE680_m6/solenv/inc -I/var/tmp/portage/app-office/openoffice-2.1.0-r1/work/ooo/build/OOE680_m6/res -I/usr/stlport -I/usr/include/stlport -I/usr/include/stlport -I/var/tmp/portage/app-office/openoffice-2.1.0-r1/work/ooo/build/OOE680_m6/solenv/inc/Xp31 -I/opt/blackdown-jdk-1.4.2.03/include -I/opt/blackdown-jdk-1.4.2.03/include/linux -I/opt/blackdown-jdk-1.4.2.03/include/native_threads/include -I/usr/include     -I/var/tmp/portage/app-office/openoffice-2.1.0-r1/work/ooo/build/OOE680_m6/solver/680/unxlngx6.pro/inc/offuh -I. -I../../../res -I. -pipe -O2 -march=x86-64 -pipe -Wno-ctor-dtor-privacy -fno-use-cxa-atexit -fvisibility-inlines-hidden -fno-exceptions    -fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DX86_64 -DCVER=C341 -DNPTL -DGLIBC=2 -DX86_64 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR -D_USE_NAMESPACE=1 -DSTLPORT_VERSION=500 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3 -DGXX_INCLUDE_PATH=/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/include/g++-v4 -DSUPD=680 -DPRODUCT -DNDEBUG -DPRODUCT_FULL -DOSL_DEBUG_LEVEL=0 -DOPTIMIZE -DEXCEPTIONS_OFF -DGSTREAMER -DCUI -DSOLAR_JAVA -DOOE680=OOE680 -DUSE_BUILTIN_RASTERIZER  -DVCL_DLLIMPLEMENTATION -DUSE_PASF -DSYSTEM_SNDFILE -DSYSTEM_PORTAUDIO -DHAVE_LIBSN -DUSE_XINERAMA -DUSE_XINERAMA_XORG -DSHAREDLIB -D_DLL_  -DMULTITHREAD  -o ../../../unxlngx6.pro/slo/salsound2.o /var/tmp/portage/app-office/openoffice-2.1.0-r1/work/ooo/build/OOE680_m6/vcl/unx/source/app/salsound2.cxx 
./salimpsound.hxx:193: error: 'PaDeviceID' does not name a type
dmake:  Error code 1, while making '../../../unxlngx6.pro/slo/salsound2.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making /var/tmp/portage/app-office/openoffice-2.1.0-r1/work/ooo/build/OOE680_m6/vcl/unx/source/app
make: *** [stamp/build] Error 1

!!! ERROR: app-office/openoffice-2.1.0-r1 failed.
Call stack:
  ebuild.sh, line 1621:   Called dyn_compile
  ebuild.sh, line 973:   Called qa_call 'src_compile'
  ebuild.sh, line 44:   Called src_compile
  openoffice-2.1.0-r1.ebuild, line 326:   Called die

wolfden
Sharecropper
Posts: 9051
Joined: Sat Jan 14, 2006 0:55
Location: Midwest USA
Contact:

Post by wolfden » Thu May 31, 2007 7:55

Well that is an older version, personally I would

emerge -C openoffice

emerge openoffice-bin

than you have the latest version and it shouldn't fail to install

smolloy
Simple Hen
Posts: 47
Joined: Wed May 02, 2007 5:24

Post by smolloy » Thu May 31, 2007 18:47

wolfden wrote:emerge -C openoffice

emerge openoffice-bin
So remove the old one, and install the binaries for the new one? I suppose that would work.

I previously had a problem emerging the non-binary form of the latest openoffice, in that it pulled down a few dependencies that didn't play nice with my system, and prevented me from being able to shut down the computer properly. I suppose I shouldn't have that problem if I use the binary version.

Thanks for your help.

Post Reply