From: "Andrey Vul" <andrey.vul@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] error emerge hal
Date: Wed, 8 Oct 2008 21:22:18 -0400 [thread overview]
Message-ID: <e38d12ff0810081822q1e89353l5ae86c393344ed7a@mail.gmail.com> (raw)
In-Reply-To: <ac564a240810081807o51e5c2c7td6e0a3b653a99ee6@mail.gmail.com>
On Wed, Oct 8, 2008 at 9:07 PM, M. Sitorus <gkjdsh@gmail.com> wrote:
> Hello,
> i'm having trouble emerging hal. Emerge stops with this error:
>
> make: *** [all] Error 2
> [31;01m* [0m
> [31;01m* [0m ERROR: sys-apps/hal-0.5.9.1-r3 failed.
> [31;01m* [0m Call stack:
> [31;01m* [0m ebuild.sh, line 49: Called src_compile
> [31;01m* [0m environment, line 3635: Called die
> [31;01m* [0m The specific snippet of code:
> [31;01m* [0m emake || die "make failed"
> [31;01m* [0m The die message:
> [31;01m* [0m make failed
> [31;01m* [0m
> [31;01m* [0m If you need support, post the topmost build error, and
> the call stack if relevant.
> [31;01m* [0m A complete build log is located at
> '/var/tmp/portage/sys-apps/hal-0.5.9.1-r3/temp/build.log'.
> [31;01m* [0m The ebuild environment file is located at
> '/var/tmp/portage/sys-apps/hal-0.5.9.1-r3/temp/environment'.
> [31;01m* [0m
>
> I have been trying to following:
> 1. revdep-rebuild
> 2. re-emerge expat
> 3. emerge the current hal installed (hal-0.5.9-r3)
>
> but emerge still doesn't work. Can you point me the problem? Thanks.
> the complete build.log is attach.
>
There is insufficient information in what you posted.
Can you post more detail?
i.e. $head -50 /var/tmp/portage/sys-apps/hal-0.5.9.1-r3/temp/build.log
--
Andrey Vul
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
next prev parent reply other threads:[~2008-10-09 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 1:07 [gentoo-user] error emerge hal M. Sitorus
2008-10-09 1:22 ` Andrey Vul [this message]
2008-10-09 1:28 ` Alex Schuster
2008-10-09 1:52 ` M. Sitorus
2008-10-13 11:43 ` M. Sitorus
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=e38d12ff0810081822q1e89353l5ae86c393344ed7a@mail.gmail.com \
--to=andrey.vul@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