From: Kevin Hanson <tuxpert@comcast.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kdewebdev-3.4.2 fails to emerge
Date: Tue, 02 Aug 2005 00:03:11 -0500 [thread overview]
Message-ID: <42EEFE8F.5030706@comcast.net> (raw)
In-Reply-To: <42EEFC32.8050105@gmail.com>
Zac Medico wrote:
> sayles@cpsc.ucalgary.ca wrote:
>
>> So this is the error message produced from emerge kdewebdev and emerge
>> --info.
>>
>> thanks again if anyone can offer help.
>>
>> -----------------------------------------------------------------
>> error message from
>> emerge kdewebdev
>>
>> !!! ERROR: kde-base/kdewebdev-3.4.2 failed.
>> !!! Function kde_src_compile, Line 169, Exitcode 2
>> !!! died running emake, kde_src_compile:make
>> !!! If you need support, post the topmost build error, NOT this status
>> message.
>>
>>
>
> That's not the whole error message. There should be more above that.
>
> Zac
Check:
http://bugs.gentoo.org/show_bug.cgi?id=100898
There is a "solution" there.
Cheers,
Kevin
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2005-08-02 5:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 2:03 [gentoo-user] kdewebdev-3.4.2 fails to emerge sayles
2005-08-02 2:13 ` Zac Medico
2005-08-02 4:37 ` sayles
2005-08-02 4:53 ` Zac Medico
2005-08-02 5:03 ` Kevin Hanson [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=42EEFE8F.5030706@comcast.net \
--to=tuxpert@comcast.net \
--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