Please add ~amd64 to the KEYWORDS for dev-games/ogre-1.0.(1/2/3) EXTRA INFORMATION IF NEEDED: OGRE, the 3D rendering engine, has worked correctly on the amd64 platform since 1.0. The OGRE 1.x ebuilds compile correctly with the ~amd64 keyword. It requires the following entries in /etc/portage/package.keywords: dev-games/cegui dev-cpp/libglademm media-gfx/nvidia-cg-toolkit (64bit Cg wasn't supported until 1.2.1) dev-libs/boost (needed because of the hardcoded mt issue when using the "threads" USE flag) Since I am not running a ~amd64 system, those would be automatically taken care of on a testing system. My game project which is developed in OGRE compiles correctly, and the ~amd64 keyword should be added to the 1.0.1, 1.0.2, and 1.0.3 ebuilds (all were tested and function correctly). Reproducible: Always Steps to Reproduce: 1. Add ~amd64 to ebuild 2. Emerge selected ~amd64 packages 3. Emerge OGRE Actual Results: Emerges correctly and compiles my existing OGRE coded application. Portage 2.0.51.22-r1 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.5-r0, 2.6.12-gentoo-r4 x86_64) ================================================================= System uname: 2.6.12-gentoo-r4 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.6.12 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.10 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.5 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="-march=k8 -pipe -O2" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -pipe -O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X alsa avi berkdb bitmap-fonts cdr cegui cg crypt cups curl devil eds encode esd fam foomaticdb fortran gif gnome gpm gstreamer gtk gtk2 imagemagick imlib ipv6 ithreads jpeg lzw lzw-tiff mad mozilla mp3 mpeg ncurses nls nptl nptlonly ogg opengl oss pam pdflib perl png python quicktime readline sdl slang spell ssl tcpd threads tiff 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
Note that the package also compiles with dev-games/ogre x86 in /etc/portage/package.keywords
Requires libglabemm-2.2.0 which is -amd64 .. Testing anyway, of course ;)
It seems that the libglademm=2.2.0 requirement isn't necessary. It works correctly with a newer version (tested with 2.4.1). In any case, it's only pulled in when the "gtk" USE flag is present. It isn't required when using the CLI OGRE interface (which is just a few questions about resolution, renderer, and bit depth before the engine starts). An ebuild edit may be helpful in this case, since the libglademm bindings are used on such a basic level in OGRE, I don't believe it would break anything.
Ignore my last comment, libglademm-2.4.1 definitely does not work correctly. It complains during ./configure. I will do some investigation.
Here I am, back again! I spoke with wumpus, a developer for the OGRE linux side of things in IRC just now. He informed me that the gtk config dialog (that's all GTK, and therefore libglademm and gtkmm is being used for) will eventually be removed, as a GLX dialog will be the default before the openGL rendering context is called. The choice of a "gtk" USE flag is unfortunate for this ebuild. It should be renamed to gtkdialog (or something similar) and made a local USE flag, as many users have it as a USE default. The usefulness of a GTK dialog box is far outweighed by the heavy dependencies which are hardly required and not necessary for any of OGRE's functionality. I'll stop distracting you all with this silly bug, but it would be nice to have OGRE through portage on my native arch. Cheers!
i'm sorry, but we'll have to wait till it effectively is removed, as we can't keyword packages which provides 90% of the functionality. Either it absolutely works, or it isn't keyworded (well, at least that's the theory :|)
