On Saturday 23 February 2008, David Corbin wrote:
> I'm getting this failure on numerous ebuilds during the umerge.   I'm at a
> loss to explain it. Any ideas?
>
> ----cut---
> /tmp/binpkgs/dev-libs/libxml2-2.6.27/temp/environment: line 265: syntax
> error near unexpected token `('
> /tmp/binpkgs/dev-libs/libxml2-2.6.27/temp/environment: line 265: `
> eval "$1() { ${ECLASS}_$1 "\$@" ; }" >/dev/null;'
> + exit 1
>  *
>  * ERROR: dev-libs/libxml2-2.6.27 failed.
>  * Call stack:
>  *               ebuild.sh, line 1641:  Called die
>  * The specific snippet of code:
>  *      preprocess_ebuild_env || \
>  *              die "error processing environment"
>  *  The die message:
>  *   error processing environment
>  *
>  * If you need support, post the topmost build error, and the call stack if
> relevant.
>  * A complete build log is located
> at '/var/log/portage/dev-libs:libxml2-2.6.27:20080223-145805.log'.
>  * The ebuild environment file is located
> at '/tmp/binpkgs/dev-libs/libxml2-2.6.27/temp/environment'.
>  *
> !!! FAILED prerm: 1
>  * The 'prerm' phase of the 'dev-libs/libxml2-2.6.27' package has failed
>  * with exit value 1. The problem occurred while executing the ebuild
>  * located at '/var/db/pkg/dev-libs/libxml2-2.6.27/libxml2-2.6.27.ebuild'.
>  * If necessary, manually remove the ebuild in order to skip the execution
>  * of removal phases.

Have you run revdep-rebuild -X -p -v and etc-update to make sure your system 
feels good lately?
-- 
Regards,
Mick

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to