There's a possibility that this problem is why ~arm isn't among this package's KEYWORDS, but I've had mostly good luck getting packages to build on a Linksys NSLU2 by adding ~arm to KEYWORDS in a copy of the ebuild in /usr/local/portage. Anyway, I get the following when I try to build gimp-print: ***** autoconf ***** configure:28141: error: possibly undefined macro: AM_PATH_GLIB If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. emerge --info: Portage 2.0.54 (uclibc/arm, gcc-3.4.4, uclibc-0.9.27-r0, 2.6.12.2 armv5teb) ================================================================= System uname: 2.6.12.2 armv5teb XScale-IXP42x Family rev 1 (v5b) Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.12 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-r1 sys-devel/binutils: 2.16-r1 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="arm" AUTOCLEAN="yes" CBUILD="armeb-softfloat-linux-uclibc" CFLAGS="-march=armv5t -mtune=xscale -Os" CHOST="armeb-softfloat-linux-uclibc" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=armv5t -mtune=xscale -Os" DISTDIR="/usr/portage/distfiles"FEATURES="autoconfig distlocks nodoc noinfo noman 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="arm berkdb bitmap-fonts bzip2 cdr cups curl dri expat foomaticdb imagemagick jpeg ncurses perl png python readline samba ssl tiff truetype truetype-fonts type1-fonts uclibc usb xml2 zlib userland_GNU kernel_linux elibc_uclibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS
you should rather use a package.keywords file instead of copying files. Oh, and you are of course supposed to be using ~arch only with ~arch, so: echo ACCEPT_KEYWORDS=~arm >> /etc/make.conf and update the deps. I guess some of them are really old. For pkges that are not in ~arm: echo cat-cat/pkg ~x86 >> /etc/portage/package.keywords good luck :)
>you should rather use a package.keywords file instead of copying files. I am using the package.keywords file. It has the following in it (among others): media-gfx/gimp-print ~arm The reason I'm copying & modifying ebuilds is that neither arm nor ~arm are included in the KEYWORDS line of the ebuild. >For pkges that are not in ~arm: >echo cat-cat/pkg ~x86 >> /etc/portage/package.keywords This seems like a nasty kludge, given that ARM != x86. FWIW, I've built the previous version (4.2.7, or whatever) of Gimp-Print without issue. v5.0, though, supports CD printing on the Epson Stylus Photo R200 and related printers. I don't think v4.2.7 does.
You should add them with ~x86 to p.keywords, here is the guide that explains you how it works: http://www.gentoo.org/doc/en/gentoo-amd64-faq.xml#keyword You do not need to add any ~arm to p.keywords, because you can add ACCEPT_KEYWORDS=~arm to your make.conf :) Flameeyes, can you please have a look at this?
Can you get the output of head -n3 on the ebuild used? emerge -pv gimp-print will show you if it takes from portage or from an overlay, if it is from overlay it might have copied from a non-fixed version.
The header from the ebuild is the following: # Copyright 1999-2006 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/media-gfx/gimp-print/gimp-print-5.0.0_rc2.ebuild,v 1.4 2006/01/28 23:14:38 flameeyes Exp $
That is exactly why you should not copy over ebuilds. You will miss important bugfixes. Really, what you are doing is not supported and we cannot help you when you are copying over stuff Try to remove the ebuild from your overlay and package.keyword it like suggested in the amd64 guide.
Hmm...seems kinda evil that two versions of an ebuild would have the same name, but upon updating to the newer ebuild and tweaking package.keywords, the slug is now (slowly) building gimp-print (it's still in ./configure as I write this). (The slug's portage tree doesn't get updated as often as it should...with only 32 MB, emerge sync (and especially emerge metadata) is slow and prone to bombing out. I have some more memory on the way for it that should fix that.) If it finishes building, I'll test it when I get home. If I can print through it, you might then want to consider adding ~arm to the ebuild's KEYWORDS.
you do not have to sync on the target machine. You can have another machine sync for you and use the tree over nfs.
