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: Re: [gentoo-user] Another error when emerging kdelibs-4.1.3-r1
Date: Wed, 19 Nov 2008 12:11:54 -0300	[thread overview]
Message-ID: <a964044f0811190711p65097c60qef13ec9ab8b4b965@mail.gmail.com> (raw)
In-Reply-To: <371ab3650811171409x423a95b1xad7e6984ecedb9a4@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1105 bytes --]

Sorry, here is the complete output (i sent it as an attach because of of its
length, I hope its not an inconvenience)

¡Thanks in advance!

2008/11/17 Espen Hustad <espen.hustad@gmail.com>

> 2008/11/17 Rafael Barrera Oro <borafael at gmail.com>:
> > 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
> >  *
> > Snip!
>
> Hi!
>
> Please post the complete build log, the lines you have posted tells
> that an error occured, not what caused it.
>
> Espen
>
>

[-- Attachment #1.2: Type: text/html, Size: 1571 bytes --]

[-- Attachment #2: build.log --]
[-- Type: application/octet-stream, Size: 372630 bytes --]

      reply	other threads:[~2008-11-19 15:13 UTC|newest]

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

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=a964044f0811190711p65097c60qef13ec9ab8b4b965@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