according to bug #82211 for amd platform, clustalx now requires =x11-libs/openmotif-2.1*. however, in x86 platform it works fine with latest version of openmotif (-2.2.3-r3). current ebuild is painfull, because during "emerge -vaDu world" it tries to upgrade to openmotif-2.2.3-r3 and next time downgrade back to openmotif-2.1. Reproducible: Always Steps to Reproduce: 1. patch clustalx-1.83-r1.ebuild 19c19 < =x11-libs/openmotif-2.1*" --- > x11-libs/openmotif" 2. emerge clustalx Actual Results: clustalx works fine Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.4.28-gentoo-r8 i686) ================================================================= System uname: 2.4.28-gentoo-r8 i686 Intel(R) Pentium(R) 4 CPU 3.40GHz Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 9 2005, 12:51:47)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.4.22-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /opt/glftpd/etc /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /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/env.d /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms" GENTOO_MIRRORS="ftp://ftp.fi.muni.cz/pub/linux/gentoo/ ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo http://gentoo.ynet.sk/pub/ ftp://gentoo.inode.at/source/ ftp://trumpetti.atm.tut.fi/gentoo/ ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo/ ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo/" MAKEOPTS="-j9" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X Xaw3d aalib acpi alsa apache2 apm arts audiofile avi bash-completion berkdb bitmap-fonts bzlib cdr crypt cups curl dga directfb divx4linux dvd emacs emacs-w3 emboss encode esd f77 fam flac font-server foomaticdb fortran gd gdbm gif gpm gtk gtk2 guile icq imagemagick imlib jack java jpeg kde leim lesstif libg++ libwww mad mikmod mmx mmx2 motif mozilla mp3 mpeg msn mule mysql ncurses nls oggvorbis opengl openssh oscar oss pam pdflib perl png python qt quicktime readline samba sdl slang sockets sox spell sqlite sse sse2 ssl svg svga tcltk tcpd tetex theora threads tiff truetype truetype-fonts type1-fonts unicode usb wxwindows xft xinerama xml xml2 xmms xosd xv xvid yahoo zlib video_cards_nvidia" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Thanks for reporting. I am not convinced this is limited to amd64; I experienced the same bug on an x86 machine. For the time being, I would rather leave it at that. If the 2.2 branch works for you, however, there is an easy workaround: the latest versions of the OpenMotif ebuilds support "SLOT"s, meaning you can have both 2.1 and 2.2 installed at the same time (thanks to Heinrich Wendel). In a nutshell, I suggest: # emerge --sync # echo "=x11-libs/openmotif-2.1.30-r11 ~x86" >> "/etc/portage/package.keywords" # echo "=x11-libs/openmotif-2.2.3-r5 ~x86" >> "/etc/portage/package.keywords" # emerge --oneshot --unmerge --ask "openmotif" # emerge --oneshot --ask "=openmotif-2.1.30-r11" "=openmotif-2.2.3-r5" Please tell me if this solves your problem.
it works ok, it is necessary to unmask also motif config echo "=x11-libs/motif-config-0.4 ~x86" >> "/etc/portage/package.keywords" thanks
I am tagging this as WONTFIX since I failed to determine why OpenMotif 2.2 will not work in some cases and there is an easy workaround. Once the new OpenMotif ebuilds are marked stable, this will not matter much anyway. Feel free to reopen if I missed something or if you have a better solution.