I tested these packages, and they are all amd64 ready: dev-java/dom4j-1.6.1 ~amd64 dev-java/msv-20050627 ~amd64 dev-java/xsdlib-20050627 ~amd64 dev-java/relaxng-datatype-1.0 ~amd64 dev-java/xpp2-2.1.10 ~amd64 dev-java/jsr173-1.0 ~amd64 dev-java/jaxme-0.3.1 ~amd64 dev-java/xmldb-20011111 ~amd64 please update them. Reproducible: Always Steps to Reproduce: my emerge info: Portage 2.0.52-r1 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r1, 2.6.13-gentoo-04-amd x86_64) ================================================================= System uname: 2.6.13-gentoo-04-amd x86_64 AMD Athlon(tm) 64 Processor 3500+ Gentoo Base System version 1.12.0_pre8 dev-lang/python: 2.4.1-r1 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 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.16.1 sys-devel/libtool: 1.5.18-r1, 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="No" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O3 -mcpu=k8 -mtune=k8 -pipe -msse -msse2 -msse3 -mmmx -fforce-addr - fomit-frame-pointer -funroll-loops -frerun-loop-opt -frerun-cse-after-loop - falign-functions=4 -fmove-all-movables -fno-ident -funit-at-a-time -fweb - funswitch-loops -fpeel-loops" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /opt/openjms/config /usr/kde/2/share/config /usr/kde/3.4/e nv /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr /lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -mcpu=k8 -mtune=k8 -pipe -msse -msse2 -msse3 -mmmx -fforce-addr - fomit-frame-pointer -funroll-loops -frerun-loop-opt -frerun-cse-after-loop - falign-functions=4 -fmove-all-movables -fno-ident -funit-at-a-time -fweb - funswitch-loops -fpeel-loops -fvisibility-inlines-hidden" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig buildpkg digest distlocks fixpackages sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ ftp://ftp.easynet.nl/mirror/gentoo/ ftp://mirror.nutsmaas.nl/gentoo/ ftp://planetmirror.com/pub/gentoo/ ftp://ftp.linux.ee/pub/gentoo/distfiles/ ftp://mirror.switch.ch/mirror/gentoo/ ftp://gentoo.risq.qc.ca/ ftp://gentoo.llarian.net/pub/gentoo ftp://gd.tuwien.ac.at/opsys/linux/gentoo/ ftp://gentoo.itdnet.net/gentoo/" LANG="hu_HU.utf8" LC_ALL="hu_HU.utf8" LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -s" LINGUAS="hu en" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="amd64 7zip X Xaw3d aac acl alsa apache2 arts artswrappersuid audiofile avi bash-completion berkdb bitmap-fonts bzip2 chroot crypt cups curl dga directfb dlloader dvd eds emboss encode erandom esd examples exif expat extensions fam firefox flac font-server foomaticdb fortran gd ggi gif glibc- omitfp gnutls gphoto2 gpm gstreamer gtk gtk2 hal howl idn imagemagick imlib innodb ipv6 ithread ithreads java javamail javascript jms jmx jpeg jpeg2k junit kde libg++ libwww lzw lzw-tiff mad mmap mp3 mpeg mpm-worker mysql ncurses nls nptl nptlonly objc ogg opengl pam pcre pdflib perl php pic png postgres python qt quicktime rdesktop readline samba sasl scanner sdl sftplogging slang sndfile snmp spell ssl symlink sysfs tcltk tcpd theora threads thunderbird tidy tiff toolbar truetype truetype-fonts type1-fonts unicode urandom usb userlocales v4l vcd vorbis xine xinerama xml xml2 xpm xv zlib linguas_hu linguas_en userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET
The amd64 arch team takes care of adding the keywords, not the developers in the java herd.
None of these are stable on the maintainer arch, so at best they can be masked ~amd64. However, this will require arch testing. I can easily verify that these will build on amd64 (note that I have NOT done so yet). However, testing is another matter, these all look like libraries (at a glance), so unless they have test suites the only way to really test them is to use a java app which depends on them. Do you have any suggestions for testing? Or does an amd64 dev want to comment on merely testing for whether it builds to mask ~amd64?
Thanks. They are all marked ~amd64 now.
In my company we use some of these packages for a huge web app. OThey works on aour servers, and so they are written in java, they should works, because this is java's filosophy. thanks for change.
