cp: cannot stat `/var/tmp/portage-pkg/gcc-3.2.1-r5/inf/files/fix_libtool_files.sh': No such file or directory chmod: failed to get attributes of `/var/tmp/portage/gcc-3.2.1-r5/temp/fix_libtool_files.sh': No such file or directory /usr/sbin/ebuild.sh: line 441: /var/tmp/portage/gcc-3.2.1-r5/temp/fix_libtool_files.sh: No such file or directory >>> Regenerating /etc/ld.so.cache... >>> sys-devel/gcc-3.2.1-r5 merged.
Err, I did not test it with a binary package, thus its entirely possible, as $FILESDIR changes for binary packages ....
sorry, no this was from source...
-------------------------------------------------------------- cp -f ${FILESDIR}/fix_libtool_files.sh ${T} chmod +x ${T}/fix_libtool_files.sh ${T}/fix_libtool_files.sh ${OLD_GCC_VERSION} -------------------------------------------------------------- Well, $T equal '/var/tmp/portage/gcc-3.2.1-r5/temp/', so $FILESDIR have to equal '/var/tmp/portage-pkg/gcc-3.2.1-r5/inf/files' if you have a look what the ebuild does .... Thus, one of following: 1) Portage changed behaviour as to what FILESDIR is set to in pkg_postinst() 2) NFI
-r6 emerged without a hitch. Thanks Az