On Thu, 2006-07-06 at 17:09 +0200, Simon Stelling wrote:
> Ciaran McCreesh wrote:
> > You can do it through bashrc. But then, if this is about working around
> > Portage's annoying lack of sane cross compile handling, why not put a
> > little effort into fixing it properly rather than a lot of effort into
> > making the tree more complicated?
>
> Err, I think you're mixing up different things.
> How should portage be
> able to do sane cross compiling if you control the instruction sets
> through use flags which are blocked in profiles the build system is
> using?
That is not the case anymore.. See PORTAGE_CONFIGROOT= and the
attachment as an example which solves this exact problem.
--
Ned Ludd <[EMAIL PROTECTED]>
Gentoo Linux
export PORTDIR=$(portageq envvar PORTDIR)
export ROOT=/dev/shm/blah
export PORTAGE_CONFIGROOT=${ROOT}
PROFILES="$(grep ^[a-z,0-9] ${PORTDIR}/profiles/profiles.desc | awk '{print
$2}' | sort -u)"
mkdir -p ${PORTAGE_CONFIGROOT}/etc/
cd ${PORTAGE_CONFIGROOT}/etc/
for p in ${PROFILES}; do
rm -f make.profile
ln -s ../../../../${PORTDIR}/profiles/${p} make.profile
touch make.conf
ls -ld $(readlink -f make.profile)
emerge --info
done
