Updating emul-linux-x86-gtklibs from 2.10.6.3 to 2.10.6.3-r1, the following error occurs: >>> /usr/lib32/libpangoxft-1.0.so.0.1400.7 >>> /usr/lib32/libpangoxft-1.0.so.0 -> libpangoxft-1.0.so.0.1400.7 !!! Cannot write to '/usr/lib32/pango'. !!! Please check permissions and directories for broken symlinks The bad symlink: $ ls -l /usr/lib32/pango lrwxrwxrwx 1 root root 36 2005-04-14 14:50 /usr/lib32/pango -> ../../emul/linux/x86/usr/lib32/pango The correct emul directory: /emul/linux/x86/usr/lib/pango Symlinking /emul/linux/x86/usr/lib32 to /emul/linux/x86/usr/lib and restarting the merge fixes this problem. Portage 2.1.2_rc4-r5 (default-linux/amd64/2006.1/desktop, gcc-4.1.1, glibc-2.5-r0, 2.6.19-gentoo-r2 x86_64) ================================================================= System uname: 2.6.19-gentoo-r2 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.12.8 Last Sync: Wed, 03 Jan 2007 12:20:01 +0000 ccache version 2.4 [enabled] dev-java/java-config: 1.3.7, 2.0.31 dev-lang/python: 2.4.4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r6 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.19 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -pipe -ggdb" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-march=k8 -O2 -pipe -ggdb -ffriend-injection" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="" FEATURES="autoconfig ccache distlocks fixpackages parallel-fetch sandbox sfperms splitdebug strict" GENTOO_MIRRORS="http://distro.ibiblio.org/pub/linux/distributions/gentoo/ http://gentoo.osuosl.org/ " LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8" LINGUAS="en" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_EXTRA_OPTS="--timeout=120" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /usr/local/bmg-main /usr/portage/local/layman/sunrise /usr/portage/local/layman/break-my-gentoo-main /usr/portage/local/layman/wrobel /usr/portage/local/layman/gentopia /usr/portage/local/layman/gnome-experimental" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="X a52 aac alsa amd64 amr bash-completion berkdb bitmap-fonts bzip2 cairo cdda cdr cli cracklib crypt css cups dbus debug dlloader dri dts dvd dvdr eds emboss encode esd fam ffmpeg firefox flac fortran gdbm gif glitz gnome gpm gstreamer gtk gtk2 hal iconv ipv6 isdnlog java jpeg kde kdehiddenvisibility ldap libg++ libnotify mad mikmod mono mp3 mpeg ncurses nls nptl nptlonly ogg opengl pam pcre perl pic png ppds pppd python qt3 qt4 quicktime readline reflection ruby samba sdl session spell spl sqlite ssl tcpd theora tiff truetype truetype-fonts type1-fonts udev unicode usb userlocales vcd vorbis x264 xcb xml xorg xv xvid zlib" ALSA_CARDS="emu10k1" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LINGUAS="en" USERLAND="GNU" VIDEO_CARDS="vesa nvidia" Unset: CTARGET, INSTALL_MASK, LDFLAGS
-r1 packages needs to be pull from the tree anyways.
*** Bug 159913 has been marked as a duplicate of this bug. ***
FWIW, I have no problems like dupe bug 159913. gtk dialogs for my 32-bit apps are fine, fonts are fine, themes are fine, etc. Perhaps that bug should be re-opened as a separate issue? This bug was strictly for a build problem which was easily worked around. It seems to me that combining these issues in a single bug would just confuse matters, but of course it's up to you, Jakub, as to what you prefer to do.
*** Bug 159961 has been marked as a duplicate of this bug. ***
*** Bug 159964 has been marked as a duplicate of this bug. ***
*** Bug 160069 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > *** Bug 160069 has been marked as a duplicate of this bug. *** > Note that when I tried app-emulation/emul-linux-x86-gtklibs-2.10.6.3 with realplay, I still had problems. Perhaps gtklibs-2.10.6.3 also has some sort of problem??
(In reply to comment #7) > Note that when I tried app-emulation/emul-linux-x86-gtklibs-2.10.6.3 with > realplay, I still had problems. Perhaps gtklibs-2.10.6.3 also has some sort of > problem?? Do you get the same error message with app-emulation/emul-linux-x86-gtklibs-2.10.6.3 ? If so, can you check if the paths in /etc/gtk-2.0/i686-pc-linux-gnu/gdk-pixbuf.loaders are correct? they should be /emul/linux/x86/usr/lib/gtk-2.0/2.10.0/loaders/....
(In reply to comment #8) > (In reply to comment #7) > > Note that when I tried app-emulation/emul-linux-x86-gtklibs-2.10.6.3 with > > realplay, I still had problems. Perhaps gtklibs-2.10.6.3 also has some sort of > > problem?? > > Do you get the same error message with > app-emulation/emul-linux-x86-gtklibs-2.10.6.3 ? If so, can you check if the > paths in /etc/gtk-2.0/i686-pc-linux-gnu/gdk-pixbuf.loaders are correct? they > should be /emul/linux/x86/usr/lib/gtk-2.0/2.10.0/loaders/... As mentioned in my first post the error message I get with 2.10.6.3 is. /opt/RealPlayer/realplay.bin: error while loading shared libraries: libgdk-x11-2.0.so.0: cannot open shared object file: No such file or directory which is fewer complaints than I got 2ith 2.10.6.3-r1. Both versions have the correct path in /etc/gtk-2.0/i686-pc-linux-gnu/gdk-pixbuf.loaders, but the 2.10.6.3-r1 does not store anything in that directory while 2.10.6.3 has 14 ".so" files. >
I just did a sync and emerge world. All is working!
-r1 has been masked and pulled from the tree.
I originally filed this bug about a bad symlink reference causing a build failure. It was turned into a different bug about general problems with the move from /emul, at which time I suggested that a different bug should be opened about those issues lest there be confusion. So now -r3 is out and...it has the same build problem I filed this bug about. Which didn't get fixed because people were dealing with the other issues. So I am reopening, setting the summary back to what I originally wrote, hoping that this time the issue I actually filed this bug for gets fixed...
this should be fixed in 10.0
