update-eix from eix-0.14.2: embe@MB-MacBook ~ $ update-eix Reading Portage settings .. Building database (/Volumes/Gentoo/var/cache/eix) .. [0] "gentoo_prefix" /Volumes/Gentoo/usr/portage/ (cache: parse|ebuild*) Reading 0% Could not start /Volumes/Gentoo/Volumes/Gentoo/usr/lib/portage/bin/ebuild.sh Reading 0% Could not properly execute /Volumes/Gentoo/usr/portage//app-admin/apache-tools/apache-tools-2.2.8-r1.ebuild Reading 0% Could not start /Volumes/Gentoo/Volumes/Gentoo/usr/lib/portage/bin/ebuild.sh Reading 0% (and so on) /Volumes/Gentoo is the value of my EPREFIX. It appears in the path twice instead of once. Removing the line containing '--with-ebuild-sh-default="${EPREFIX}/usr/$(get_libdir)/portage/bin/ebuild.sh"' from the ebuild fixes this for me (eix seems to automatically prefix the EPREFIX to this path).
(In reply to comment #0) > Removing the line containing > '--with-ebuild-sh-default="${EPREFIX}/usr/$(get_libdir)/portage/bin/ebuild.sh"' This line should be the same as it is in the x86 ebuild: --with-ebuild-sh-default="/usr/$(get_libdir)/portage/bin/ebuild.sh" The "%{EPREFIX_PORTAGE_EXEC}" is automagically prefixed to the passed value. To avoid a similar misunderstanding for the forthcoming eix-0.14.3: There will be two further variables PORTAGE_BIN_PATH and PORTAGE_ROOT_PATH whose defaults can be set; they will just passed "as-is" (without prefixing something) to the ebuild.sh script. So, as far as I can see, also for their defaults there should be just the values used which are present when the ebuild is executed.
Thanks Martin for the explanation, fixed.
