Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
pkgs fail - libxml, or index.docbook or .cache? [Solved]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 874
Location: Alaska

PostPosted: Sun Oct 05, 2008 10:27 pm    Post subject: pkgs fail - libxml, or index.docbook or .cache? [Solved] Reply with quote

I recently updated world and then did revdep-rebuild and all the packages, like digikam, amarok. evince, vmware-server, etc. are failing with similar errors:
Code:
/bin/sh ../../../libtool --silent --tag=CXX --mode=link i686-pc-linux-gnu-g++  -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -march=prescott -O2 -pipe -fomit-frame-pointer -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION   -Wl,-O1 -o amarokcollectionscanner -L/usr/kde/3.5/lib -L/usr/qt/3/lib     -L/usr/kde/3.5/lib -R /usr/lib -R /usr/kde/3.5/lib -R /usr/qt/3/lib -R /usr/kde/3.5/lib main.o collectionscannerdcophandler.o collectionscanner.o collectionscannerdcopiface_skel.o ../../../amarok/src/metadata/libmetadata.la ../../../amarok/src/libamarok.la -lqt-mt  -lz -lpng -lz -lm -lXext -lX11  -lSM -lICE -lpthread -lkdecore -ltag
make[4]: Leaving directory `/var/tmp/portage/media-sound/amarok-1.4.10-r1/work/amarok-1.4.10/amarok/src/collectionscanner'
make[3]: Leaving directory `/var/tmp/portage/media-sound/amarok-1.4.10-r1/work/amarok-1.4.10/amarok/src'
make[3]: Entering directory `/var/tmp/portage/media-sound/amarok-1.4.10-r1/work/amarok-1.4.10/amarok'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/var/tmp/portage/media-sound/amarok-1.4.10-r1/work/amarok-1.4.10/amarok'
make[2]: Leaving directory `/var/tmp/portage/media-sound/amarok-1.4.10-r1/work/amarok-1.4.10/amarok'
Making all in doc
make[2]: Entering directory `/var/tmp/portage/media-sound/amarok-1.4.10-r1/work/amarok-1.4.10/doc'
Making all in amarok
make[3]: Entering directory `/var/tmp/portage/media-sound/amarok-1.4.10-r1/work/amarok-1.4.10/doc/amarok'
/usr/kde/3.5/bin/meinproc --check --cache index.cache.bz2 ./index.docbook
Warning: program compiled against libxml 207 using older 206
make[3]: *** [index.cache.bz2] Error 1
make[3]: Leaving directory `/var/tmp/portage/media-sound/amarok-1.4.10-r1/work/amarok-1.4.10/doc/amarok'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/media-sound/amarok-1.4.10-r1/work/amarok-1.4.10/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/media-sound/amarok-1.4.10-r1/work/amarok-1.4.10'
make: *** [all] Error 2
 *
 * ERROR: media-sound/amarok-1.4.10-r1 failed.
 Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 4082:  Called kde_src_compile
 *             environment, line 2900:  Called kde_src_compile 'src_compile'
 *             environment, line 3025:  Called kde_src_compile 'src_compile' 'all' 'myconf'
 *             environment, line 3021:  Called die
 * The specific snippet of code:
 *                   emake || die "died running emake, $FUNCNAME:make"
 *  The die message:
 *   died running emake, kde_src_compile:make



help appreciated! cheers, Jim

PS: and I did try re-emerging libxml2 and in my USE flags I have -doc.


Last edited by hunky on Fri Oct 10, 2008 3:18 am; edited 2 times in total
Back to top
View user's profile Send private message
notHerbert
Advocate
Advocate


Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W

PostPosted: Mon Oct 06, 2008 11:33 am    Post subject: Reply with quote

Please post output of emerge --info
Back to top
View user's profile Send private message
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 874
Location: Alaska

PostPosted: Mon Oct 06, 2008 4:25 pm    Post subject: Reply with quote

Thanks for looking notHerbert,
Code:
 # emerge --info
Portage 2.1.4.4 (default/linux/x86/2008.0, gcc-4.1.2, glibc-2.6.1-r0, 2.6.26-gentoo-r1 i686)
=================================================================
System uname: 2.6.26-gentoo-r1 i686 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz
Timestamp of tree: Mon, 06 Oct 2008 00:00:01 +0000
ccache version 2.4 [enabled]
app-shells/bash:     3.2_p33
dev-java/java-config: 1.3.7, 2.1.6
dev-lang/python:     2.4.4-r13, 2.5.2-r7
dev-python/pycrypto: 2.0.1-r6
dev-util/ccache:     2.4-r7
sys-apps/baselayout: 1.12.11.1
sys-apps/sandbox:    1.2.18.1-r2
sys-devel/autoconf:  2.13, 2.61-r2
sys-devel/automake:  1.4_p6, 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1-r1
sys-devel/binutils:  2.18-r3
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   1.5.26
virtual/os-headers:  2.6.23-r3
ACCEPT_KEYWORDS="x86"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=prescott -O2 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-march=prescott -O2 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache distlocks fixpackages metadata-transfer parallel-fetch sandbox sfperms unmerge-orphans userfetch"
GENTOO_MIRRORS="http://mirror.usu.edu/mirrors/gentoo/ http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
LDFLAGS="-Wl,-O1"
LINGUAS="en en_US"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/portage/local/layman/pro-audio /usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X aac acl aiglx alsa apache2 berkdb bitmap-fonts bzip2 cairo cdr cli cracklib crypt css cups dbus divx4linux dlloader dri dvd dvdr exif fam flac font foomatic fortran gdbm gif gimp gimpprint gphoto2 gpm hal iconv imagemagick ipv6 isdnlog ithreads jack jack-tmpfs jackmidi java jpeg kde kipi ladspa midi mmx mozilla mp3 mudflap musicbrainz mysql ncurses nfs nls nptl nptlonly nsplugin nvidia opengl openmp oss pam pcre pda perl png ppds pppd python qt3 readline real reflection rtc samba scanner session sndfile spell spl sse ssl stream svg sysfs tcpd tga theora tiff truetype-fonts type1-fonts unicode usb vorbis win32codecs x86 xanim xcomposite xinerama xorg xrandr xulrunner xvid zlib"
ALSA_CARDS="ice1712"
ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol"
APACHE2_MODULES="actions alias auth_basic auth_digest authn_anon authn_dbd authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock dbd deflate dir disk_cache env expires ext_filter file_cache filter headers ident imagemap include info log_config logio mem_cache mime mime_magic negotiation proxy proxy_ajp proxy_balancer proxy_connect proxy_http rewrite setenvif so speling status unique_id userdir usertrack vhost_alias" CAMERAS="canon"
ELIBC="glibc"
INPUT_DEVICES="evdev keyboard mouse wacom"
KERNEL="linux"
LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text"
LINGUAS="en en_US"
USERLAND="GNU"
VIDEO_CARDS="nvidia vesa fbdev vga"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Back to top
View user's profile Send private message
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 874
Location: Alaska

PostPosted: Mon Oct 06, 2008 10:27 pm    Post subject: Reply with quote

for more info, here's the digikam error:
Code:
Good - your configure finished. Start make now

make  all-recursive
make[1]: Entering directory `/var/tmp/portage/media-gfx/digikam-0.9.4/work/digikam-doc-0.9.4'
Making all in doc
make[2]: Entering directory `/var/tmp/portage/media-gfx/digikam-0.9.4/work/digikam-doc-0.9.4/doc'
Making all in digikam
make[3]: Entering directory `/var/tmp/portage/media-gfx/digikam-0.9.4/work/digikam-doc-0.9.4/doc/digikam'
/usr/kde/3.5/bin/meinproc --check --cache index.cache.bz2 ./index.docbook
Warning: program compiled against libxml 207 using older 206
make[3]: *** [index.cache.bz2] Error 1
make[3]: Leaving directory `/var/tmp/portage/media-gfx/digikam-0.9.4/work/digikam-doc-0.9.4/doc/digikam'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/media-gfx/digikam-0.9.4/work/digikam-doc-0.9.4/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/media-gfx/digikam-0.9.4/work/digikam-doc-0.9.4'
make: *** [all] Error 2
 *
 * ERROR: media-gfx/digikam-0.9.4 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 4072:  Called kde_src_compile
 *             environment, line 2900:  Called kde_src_compile 'src_compile'
 *             environment, line 3025:  Called kde_src_compile 'src_compile' 'all' 'myconf'
 *             environment, line 3021:  Called die
 * The specific snippet of code:
 *                   emake || die "died running emake, $FUNCNAME:make"
 *  The die message:
 *   died running emake, kde_src_compile:make
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/media-gfx/digikam-0.9.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/media-gfx/digikam-0.9.4/temp/environment'.
 *

 * Messages for package media-gfx/digikam-0.9.4:

 * Enabling translations for: en
 * Enabling documentation for: en
 *
 * ERROR: media-gfx/digikam-0.9.4 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 4072:  Called kde_src_compile
 *             environment, line 2900:  Called kde_src_compile 'src_compile'
 *             environment, line 3025:  Called kde_src_compile 'src_compile' 'all' 'myconf'
 *             environment, line 3021:  Called die
 * The specific snippet of code:
 *                   emake || die "died running emake, $FUNCNAME:make"
 *  The die message:
 *   died running emake, kde_src_compile:make
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/media-gfx/digikam-0.9.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/media-gfx/digikam-0.9.4/temp/environment'.
Back to top
View user's profile Send private message
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 874
Location: Alaska

PostPosted: Tue Oct 07, 2008 7:09 am    Post subject: Reply with quote

I have been searching and found this similar thread from 2005:
https://forums.gentoo.org/viewtopic-t-407988-highlight-index+cache+bz2+error+139.html so thought I would try a
emerge -e world and sheesh I have nearly 1000 packages. I guess I like to try a lot of different things. So the irritating part of this is packages fail to emerge occasionally so I have to keep an eye on it. I'm at 370 packages to go now and I suppose it'll break again when I go to bed here shortly.

But for added data points, the packages that have so far failed to emerge are ktraynetworker, kflicker, kdiff3, and media-sound/kid3. So far the only one I've confirmed that failed with the same kind of error as in my parent message is kflicker. (the others had scrolled out of the bash buffer.)

That thread above mentioned re-emerging libxml2 and libxslt which I've done to no avail. I had run python-updater a day or so ago to make sure that wasn't it. Not sure what else may need similar treatment. I had done the gcc migration from 3.6 to 4.whatever according to the guides back when that happened. Anything I might be missing?

thanks, Jim

[edit] A couple more failures:
libxcb
tellico
gnome-doc-utils (symbol lookup libxslt.so.1 error)
hal (same kind of error - 150 packages to go...)
kpowersave
k3b

Well - I lost my emerge (resume didn't bring it back after I tried using "perl-cleaner all" and testing another emerge (thought I could do it but obviously not. So I didn't finish the last 140 packages or so - but I don't know - didn't seem like it was working out.
Lots of those "warning: program compiled against libxml 207 using older 206" errors.

I did just recently upgrade my kernel from gentoo-sources-2.6.19 up to 2.6.26 - could I have missed something there?

So I've about exhausted my research capabilities - if anyone can help I would appreciate it. /jd
Back to top
View user's profile Send private message
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 874
Location: Alaska

PostPosted: Tue Oct 07, 2008 5:37 pm    Post subject: Reply with quote

This message "warning: program compiled against libxml 207 using older 206" is giving me grief. I looked in /var/log/messages just poking around and found the following - may be of interest since it refers to xml. I'm stumbling around in the dark..

Code:
Oct  7 09:16:55 jad (jim-31933): SIGHUP received, reloading all databases
Oct  7 09:16:55 jad (jim-31933): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Oct  7 09:16:55 jad (jim-31933): Resolved address "xml:readwrite:/home/jim/.gconf" to a writable configuration source at position 1
Oct  7 09:16:55 jad (jim-31933): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Oct  7 09:16:55 jad (jim-31933): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 3
Oct  7 09:16:55 jad (jim-31933): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 4
Oct  7 09:16:55 jad (jim-31933): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 5
Oct  7 09:16:55 jad (jim-31933): Resolved address "xml:readwrite:/home/jim/.gconf" to a writable configuration source at position 6
Oct  7 09:16:55 jad (jim-31933): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 7


I did a search for index.cache.bz2 using locate (on my computer) and besides a whole bunch in /usr/kde/3.5/share/doc/HTML/en/<various packages>/,

there's a list here of my failed packages:
Code:
/usr/share/doc/HTML/da/kdiff3/index.cache.bz2
/usr/share/doc/HTML/da/krecipes/index.cache.bz2
/usr/share/doc/HTML/de/kid3/index.cache.bz2
/usr/share/doc/HTML/de/kpowersave/index.cache.bz2
/usr/share/doc/HTML/de/kdiff3/index.cache.bz2
/usr/share/doc/HTML/cs/kpowersave/index.cache.bz2
/usr/share/doc/HTML/en/k3b/index.cache.bz2
/usr/share/doc/HTML/en/kid3/index.cache.bz2
/usr/share/doc/HTML/en/kflickr/index.cache.bz2
/usr/share/doc/HTML/en/digikam/index.cache.bz2
/usr/share/doc/HTML/en/kpowersave/index.cache.bz2
/usr/share/doc/HTML/en/ktraynetworker/index.cache.bz2
/usr/share/doc/HTML/en/tellico/index.cache.bz2
/usr/share/doc/HTML/en/amarok/index.cache.bz2
/usr/share/doc/HTML/en/basket/index.cache.bz2
/usr/share/doc/HTML/en/kdiff3/index.cache.bz2
/usr/share/doc/HTML/en/krecipes/index.cache.bz2
/usr/share/doc/HTML/en/krusader/index.cache.bz2
/usr/share/doc/HTML/en/gwenview/index.cache.bz2
/usr/share/doc/HTML/es/kdiff3/index.cache.bz2
/usr/share/doc/HTML/es/krecipes/index.cache.bz2
/usr/share/doc/HTML/et/kdiff3/index.cache.bz2
/usr/share/doc/HTML/et/krecipes/index.cache.bz2
/usr/share/doc/HTML/fi/kpowersave/index.cache.bz2
/usr/share/doc/HTML/fr/tellico/index.cache.bz2
/usr/share/doc/HTML/fr/kdiff3/index.cache.bz2
/usr/share/doc/HTML/hu/kpowersave/index.cache.bz2
/usr/share/doc/HTML/it/kdiff3/index.cache.bz2
/usr/share/doc/HTML/nb/kpowersave/index.cache.bz2
/usr/share/doc/HTML/nl/kdiff3/index.cache.bz2
/usr/share/doc/HTML/pt/kdiff3/index.cache.bz2
/usr/share/doc/HTML/pt/krecipes/index.cache.bz2
/usr/share/doc/HTML/ru/krusader/index.cache.bz2
/usr/share/doc/HTML/sv/kdiff3/index.cache.bz2
/usr/share/doc/HTML/sv/krecipes/index.cache.bz2
Back to top
View user's profile Send private message
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 874
Location: Alaska

PostPosted: Wed Oct 08, 2008 4:49 pm    Post subject: Reply with quote

I asked the question over at a mailing list with the xml people about my error message
"Warning: compiled against libxml 207 using older 206" and I got this:
Quote:

This means you have programs which were compiled agaisnt libxml2-2.7.x
but at runtime the shared library found is an old 2.6.x one. The solution
is to make sure you have an installed version libxml2-2.7.x and that
programs are using it !


I have tried emerge -Cp libxml2 and all it shows is libxml2-2.7.2. I do see some older 2.6 versions under vmware-server's vmware-vix and under openoffice. But not much elsewhere. Of course I haven't cleaned out the portage cache's under /var and the distfiles so older versions show up there too but that shouldn't matter.

I'm very willing to solve this problem since I can no longer run revdep-rebuild or re-install some apps.

cheers, Jim
Back to top
View user's profile Send private message
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 874
Location: Alaska

PostPosted: Wed Oct 08, 2008 9:43 pm    Post subject: Reply with quote

Gimp fails similarly
Code:
gtk-doc: Building HTML
rm -rf ./html
mkdir ./html
cd ./html && gtkdoc-mkhtml libgimpbase ../libgimpbase-docs.sgml
Warning: program compiled against libxml 207 using older 206
/usr/bin/xsltproc: symbol lookup error: /usr/lib/libxslt.so.1: undefined symbol: xmlXPathCompiledEvalToBoolean
make[3]: *** [html-build.stamp] Error 127
make[3]: Leaving directory `/var/tmp/portage/media-gfx/gimp-2.6.0/work/gimp-2.6.0/devel-docs/libgimpbase'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/media-gfx/gimp-2.6.0/work/gimp-2.6.0/devel-docs'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/media-gfx/gimp-2.6.0/work/gimp-2.6.0'
make: *** [all] Error 2
 *
 * ERROR: media-gfx/gimp-2.6.0 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 3137:  Called gnome2_src_compile
 *             environment, line 2217:  Called die
 * The specific snippet of code:
 *       emake || die "compile failure"
 *  The die message:
 *   compile failure
 


I've got libxslt-1.1.24-r1 installed. (and reinstalled). And libxml2-2.7.2 (and re-installed).

Next step, before wiping my system completely, would possibly be a bug report but not sure under which category to place it. Maybe just libxml?

cheers, Jim
Back to top
View user's profile Send private message
desultory
Bodhisattva
Bodhisattva


Joined: 04 Nov 2005
Posts: 9410

PostPosted: Thu Oct 09, 2008 8:51 am    Post subject: Reply with quote

Before filing a bug report check for orphaned versions of libxml2, run locate libxml2.so and qfile -v `locate libxml2.so`, that will require both app-portage/portage-utils and sys-apps/slocate to be presently installed on that system.
Back to top
View user's profile Send private message
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 874
Location: Alaska

PostPosted: Thu Oct 09, 2008 3:58 pm    Post subject: Reply with quote

thanks for helping!
Code:
locate libxml2.so
/opt/vmware/server/lib/lib/libxml2.so.2
/opt/vmware/server/lib/lib/libxml2.so.2/libxml2.so.2
/opt/vmware/server/lib/vmware-vix/lib/libxml2.so.2.6.26
/opt/vmware/server/lib/vmware-vix/lib/libxml2.so.2
/opt/vmware/server/lib/vmware-vix/lib/VIServer-2.0.0/32bit/libxml2.so.2.6.26
/opt/vmware/server/lib/vmware-vix/lib/VIServer-2.0.0/32bit/libxml2.so.2
/opt/vmware/server/lib/vmware-vix/lib/libxml2.so
/usr/lib/libxml2.so.2
/usr/lib/libxml2.so.2.7.2
/usr/lib/libxml2.so
/usr/lib/openoffice/program/libxml2.so.2.6.17.1
/usr/lib/openoffice/program/libxml2.so.2.6.17
/usr/lib/openoffice/program/libxml2.so.2
/usr/lib/openoffice/program/libxml2.so
/home/jim/.mozilla/firefox/abxitris.default/extensions/VMwareVMRC@vmware.com/plugins/lib/libxml2.so.2
/home/jim/.mozilla/firefox/abxitris.default/extensions/VMwareVMRC@vmware.com/plugins/lib/libxml2.so.2/libxml2.so.2

Code:
qfile -v `locate libxml2.so`
app-emulation/vmware-vix-1.6.0.116503 (/opt/vmware/server/lib/vmware-vix/lib/libxml2.so.2.6.26)
app-emulation/vmware-vix-1.6.0.116503 (/opt/vmware/server/lib/vmware-vix/lib/libxml2.so.2)
app-emulation/vmware-vix-1.6.0.116503 (/opt/vmware/server/lib/vmware-vix/lib/VIServer-2.0.0/32bit/libxml2.so.2.6.26)
app-emulation/vmware-vix-1.6.0.116503 (/opt/vmware/server/lib/vmware-vix/lib/VIServer-2.0.0/32bit/libxml2.so.2)
app-emulation/vmware-vix-1.6.0.116503 (/opt/vmware/server/lib/vmware-vix/lib/libxml2.so)
app-emulation/vmware-server-2.0.0.116503 (/opt/vmware/server/lib/lib/libxml2.so.2)
app-emulation/vmware-server-2.0.0.116503 (/opt/vmware/server/lib/lib/libxml2.so.2/libxml2.so.2)
app-office/openoffice-bin-2.4.1 (/usr/lib/openoffice/program/libxml2.so.2.6.17.1)
app-office/openoffice-bin-2.4.1 (/usr/lib/openoffice/program/libxml2.so.2.6.17)
app-office/openoffice-bin-2.4.1 (/usr/lib/openoffice/program/libxml2.so.2)
app-office/openoffice-bin-2.4.1 (/usr/lib/openoffice/program/libxml2.so)
dev-libs/libxml2-2.7.2 (/usr/lib/libxml2.so.2)
dev-libs/libxml2-2.7.2 (/usr/lib/libxml2.so.2.7.2)
dev-libs/libxml2-2.7.2 (/usr/lib/libxml2.so)
Back to top
View user's profile Send private message
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 874
Location: Alaska

PostPosted: Fri Oct 10, 2008 3:17 am    Post subject: Reply with quote

I can go away again (until the next problem anyway) as I've figured out how to fix it but don't know why things broke like they did
Vmware-vix had installed the older version of libxml-2.6.26 in its own install directory but for some reason some other packages were picking it up instead of the proper one. I uninstalled vmware-vix and things are acting normal again.

As vmware-vix is unsupported software (I think) so I doubt anyone will want to waste much time figuring it out - but the question does remain: why were all the failing packages picking up the libxml from vmware-vix's directory instead of the proper directory? Maybe it is an easy answer. But really glad I got things working and don't really need the vmware-vix program as it has served its purpose.


Thanks for looking.
Back to top
View user's profile Send private message
desultory
Bodhisattva
Bodhisattva


Joined: 04 Nov 2005
Posts: 9410

PostPosted: Fri Oct 10, 2008 3:42 am    Post subject: Reply with quote

hunky wrote:
As vmware-vix is unsupported software (I think) so I doubt anyone will want to waste much time figuring it out - but the question does remain: why were all the failing packages picking up the libxml from vmware-vix's directory instead of the proper directory?
It is, what overlay did you install it from? As for why it caused that behavior, the short answer is that it was not properly sandboxed so it effectively leaked libraries.
Back to top
View user's profile Send private message
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 874
Location: Alaska

PostPosted: Fri Oct 10, 2008 3:50 am    Post subject: Reply with quote

don't want to poke fingers but a very helpful fellow over at:
https://forums.gentoo.org/viewtopic-t-704233-start-25.html

I was having trouble getting vmware-server to work and he helped - he offered the program to try to get vmware-tools installed via command line. I have gone ahead and placed a warning at the end of that thread so I'm sure he'll see it.

Short answer: not in an overlay (I don't think) - an independent ebuild.
Back to top
View user's profile Send private message
desultory
Bodhisattva
Bodhisattva


Joined: 04 Nov 2005
Posts: 9410

PostPosted: Fri Oct 10, 2008 5:35 am    Post subject: Reply with quote

Not a problem, and no reason to worry about blame, I was mostly wondering how much work would be involved in fixing the problem.
Back to top
View user's profile Send private message
Poikilotherm
n00b
n00b


Joined: 13 Aug 2007
Posts: 4
Location: Germany

PostPosted: Tue Dec 02, 2008 6:24 pm    Post subject: Reply with quote

Hello dear friends of Gentoo,

I had a very similiar problem here with /usr/bin/kde/3.5/meinproc as described by the original author.

It took me about 1 hour to figure out what the real problem was, as I did not have installed vmware-vix.

At first I took a glance at an `ldd /usr/bin/kde/3.5/meinproc` - and gess what I saw?
"libxml2.so.2 => /usr/lib/openoffice/ure/lib/libxml2.so.2"

It came with the binary version of Open-Office 3.
The real problem behind all this is LDPATH.
If you check-out ldconfig -p for libxml, it shows multiple entries for libxml2.so.2.

Asking myself what all this is based on, I gave a `grep LD /etc/env.d/*` a try - and there were a lot of files configuring that enviroment-var.
One could say no problem - but nowhere a "LDPATH="/usr/lib"" is definded - on /etc/env.d/00basic is only LDPATH="/usr/local/bin".

After changing that into "LDPATH="/usr/lib:/usr/local/lib"" and an simple env-update (which inherits a run of ldconfig) everything was fine - /usr/lib/libxml2.so.2 was taken as first choice for this library and I could successfully compile everything that failed before. (`ldd /usr/bin/kde/3.5/meinproc` showed me "libxml2.so.2 => /usr/lib/libxml2.so.2 (0xb6aaf000)" now...)

So - Is this a bug or not? Perhaps this path should be added to the baselayout in env.d... Hope it helps others searching for this...
_________________
System: Thinkpad R60 - Intel C2D T5300, 4G RAM - Gentoo 2008.0 Kernel 2.6.27 - GCC 4.1.2, march = nocona, -O2 - portage 2.2_rc16
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum