I have checked the code for eurosym, and have successfully compiled and installed dev-tex/eurosym-1.4 for amd64; without any modifications needed from the x86 code base. From what I have seen on the compiler commands, the x86 code base, grabs the values from make.conf; thus allowing anyone to compile on a amd64 based system and compiling in amd68 mode. Reproducible: Always Steps to Reproduce: 1. 2. 3. Portage 2.0.51.22-r2 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r1, 2.6.11-gentoo-r11 x86_64) ================================================================= System uname: 2.6.11-gentoo-r11 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.12.0_pre7 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.11 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 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=k8" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib64/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/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=k8" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.osuosl.org/" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="amd64 X a52 alsa avi bash-completion berkdb bitmap-fonts bzip2 cdr crypt cups curl doc dvd eds encode esd fam flac foomaticdb fortran gd gdbm gif gnome gpm gstreamer gtk gtk2 hal imagemagick imlib ipv6 java jpeg junit kde kerberos libwww lzw lzw-tiff mad motif mozilla mp3 mpeg ncurses nls nvidia ogg oggvorbis opengl oss pam pdflib perl plotutils png python qt quicktime readline ruby sdl spell ssl tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts usb userlocales vorbis xml2 xpm xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTDIR_OVERLAY
This ebuild seems to want tetex-1, which is masked (missing keyword). The current amd64 version is tetex-2, and ~amd64 is tetex-3. Does the ebuild actually require tetex-1, or can it use the later versions? Without more info on why tetex-1 is required, I'm not really willing to test tetex-1 for keywording (given that two versions later is already keyworded).
I did some reading. The eurosym package is apparently already included in tetex-2 and later. Is there a reason why people are still installing tetex-1 ? If so, we'll need a bug asking for tetex-1 to be keyworded ~amd64 and then we can move on to this bug.
I have been doing some additional testing with that package, from what I can see tetex-2 and 3, don't need to have that installed. Also I have been seeing the package cause some other interferances; (not tetex directly, as it didn't care either way if it was installed or not); with some of my other packages that was installed with it. Unless anyone wants it still, lets keep it as it is, and not keyword ~amd64 it for now.
we're currently testing a new alias system, sorry for the bugspam
Apparently fixed in later (and already keyworded) verions of tetex
