public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: James Ausmus <james.ausmus@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Failure updating to gdbm-1.8.3-r4
Date: Mon, 18 Jan 2010 12:54:30 -0800	[thread overview]
Message-ID: <b79f23071001181254yeecc47t199a48f9d8c1779e@mail.gmail.com> (raw)
In-Reply-To: <EE282393-1994-49B7-8404-09587C453E5D@gmail.com>

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

On Mon, Jan 18, 2010 at 12:50 PM, Daniel Dilts <dilts.daniel@gmail.com>wrote:

> I'm running the no-multilib version of gentoo-amd64 on a Core2 duo.
>> When I try to run emerge --update --deep --newuse world I get the
>> following error:
>>
>
> <snip>
>
>
>> * If you need support, post the topmost build error, and the call stack if
>> relevant.
>>
>
> <snip>
>
> Please do as the error message suggests, and post the topmost build error -
> the info you posted does not contain anything that can help root cause the
> issue.
>
>
> The only other error type thing I can find (didn't find it before because
> of vim's default case sensitive search) is:
>
> mv -f .libs/gdbmfetch.lo gdbmfetch.lo
> make: *** [gdbmdelete.lo] Error 1
> make: *** Waiting for unfinished jobs....
> mv -f .libs/gdbmopen.lo gdbmopen.lo
>
> Followed immediately by the last bit that I posted.
>

Hmm, it looks like it might still be higher up than that - try just visually
scanning upwards a bit from that point (it can actually be quite a bit
higher, if there are multiple make jobs running in parallel - ie.
MAKEOPTS="-j2" or more). Alternately, attach the build log, and we can take
a look through it. :)

-James

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

      reply	other threads:[~2010-01-18 20:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18 20:37 [gentoo-amd64] Failure updating to gdbm-1.8.3-r4 Daniel Dilts
2010-01-18 20:43 ` Markos Chandras
2010-01-18 20:44 ` James Ausmus
2010-01-18 20:50   ` Daniel Dilts
2010-01-18 20:54     ` James Ausmus [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=b79f23071001181254yeecc47t199a48f9d8c1779e@mail.gmail.com \
    --to=james.ausmus@gmail.com \
    --cc=gentoo-amd64@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