This looks like a case where configure has failed to replace @BASH@ with a path to bash. All the scripts in the work dir (/opt/gentoo/var/tmp/portage/sys-apps/portage-2.2.00.9271/work/prefix-portage-2.2.00.9271/bin) have #!@BASH@ at the top of them._________________--
_jsn

for f in $EPREFIX/usr/lib/portage/bin/*
do
ln -s $f $EPREFIX/usr/bin/
done

The "#!@BASH@: bad interpreter" error is a result of putting ./bin at the end of my path. When bash can't find emake higher up -- in $EPREFIX/usr/bin, for example -- it goes ahead and calls ./bin/emake in the install directory, which of course hasn't had a shell substituted into it yet.

If I remove ./bin from my path, I just get "emake: command not found", so evidently something is not right with the way portage is bootstrapped into place. Is it a bug that the symlinks I mention above are not created automatically?_________________--
_jsn