public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rafael Barrera Oro" <borafael@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Another error when emerging kdelibs-4.1.3-r1
Date: Mon, 17 Nov 2008 10:01:34 -0300	[thread overview]
Message-ID: <a964044f0811170501r2ef3ea55jc449914f1b92381@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2425 bytes --]

Not to long ago i started a thread about an ACCESS ERROR VIOLATION that
happened any time i tried to emerge kde-meta (i ended up submiting a bug).
Now the problem has changed, for some reason. What happens now is that the
emerge process dies when it reaches the point where it builds the nepomuk
target. This happens at 50% which is weird since the other error happened at
the 90% or later.

Here is some of the outcome:

[ 50%] Building CXX object
nepomuk/core/CMakeFiles/nepomuk.dir/nepomuk_automoc.o
Linking CXX shared library ../../lib/libnepomuk.so
[ 50%] Built target nepomuk
make: *** [all] Error 2
 *
 * ERROR: kde-base/kdelibs-4.1.3-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 3119:  Called kde4-base_src_compile
 *             environment, line 2361:  Called kde4-base_src_make
 *             environment, line 2396:  Called cmake-utils_src_make
 *             environment, line  851:  Called die
 * The specific snippet of code:
 *           emake "$@" || die "Make failed!";
 *  The die message:
 *   Make failed!
 *
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/var/tmp/portage/kde-base/kdelibs-4.1.3-r1/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/kde-base/kdelibs-4.1.3-r1/temp/environment'.
 *

>>> Failed to emerge kde-base/kdelibs-4.1.3-r1, Log file:

>>>  '/var/tmp/portage/kde-base/kdelibs-4.1.3-r1/temp/build.log'

 * Messages for package kde-base/kdelibs-4.1.3-r1:

 *
 * ERROR: kde-base/kdelibs-4.1.3-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 3119:  Called kde4-base_src_compile
 *             environment, line 2361:  Called kde4-base_src_make
 *             environment, line 2396:  Called cmake-utils_src_make
 *             environment, line  851:  Called die
 * The specific snippet of code:
 *           emake "$@" || die "Make failed!";
 *  The die message:
 *   Make failed!
 *
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/var/tmp/portage/kde-base/kdelibs-4.1.3-r1/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/kde-base/kdelibs-4.1.3-r1/temp/environment'.
 *

As usual, thanks in advance people

take care

Rafael

[-- Attachment #2: Type: text/html, Size: 3708 bytes --]

             reply	other threads:[~2008-11-17 13:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-17 13:01 Rafael Barrera Oro [this message]
2008-11-17 22:09 ` [gentoo-user] Another error when emerging kdelibs-4.1.3-r1 Espen Hustad
2008-11-19 15:11   ` Rafael Barrera Oro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a964044f0811170501r2ef3ea55jc449914f1b92381@mail.gmail.com \
    --to=borafael@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox