* [gentoo-amd64] Failure updating to gdbm-1.8.3-r4
@ 2010-01-18 20:37 Daniel Dilts
2010-01-18 20:43 ` Markos Chandras
2010-01-18 20:44 ` James Ausmus
0 siblings, 2 replies; 5+ messages in thread
From: Daniel Dilts @ 2010-01-18 20:37 UTC (permalink / raw
To: gentoo-amd64
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
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:
*
* ERROR: sys-libs/gdbm-1.8.3-r4 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2916: Called die
* The specific snippet of code:
* emake || die
* The die message:
* (no error message)
*
* 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/sys-libs/gdbm-1.8.3-r4/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/gdbm-1.8.3-r4/temp/environment'.
*
Any ideas what I can do to fix this error?
[-- Attachment #2: Type: text/html, Size: 2558 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-amd64] Failure updating to gdbm-1.8.3-r4
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
1 sibling, 0 replies; 5+ messages in thread
From: Markos Chandras @ 2010-01-18 20:43 UTC (permalink / raw
To: gentoo-amd64
[-- Attachment #1: Type: Text/Plain, Size: 1117 bytes --]
On Monday 18 January 2010 22:37:01 Daniel Dilts 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:
>
> *
> * ERROR: sys-libs/gdbm-1.8.3-r4 failed.
> * Call stack:
> * ebuild.sh, line 49: Called src_compile
> * environment, line 2916: Called die
> * The specific snippet of code:
> * emake || die
> * The die message:
> * (no error message)
> *
> * 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/sys-libs/gdbm-1.8.3-r4/temp/build.log'. * The ebuild
> environment file is located at
> '/var/tmp/portage/sys-libs/gdbm-1.8.3-r4/temp/environment'. *
>
>
> Any ideas what I can do to fix this error?
>
Please fill a bug report on http://bugs.gentoo.org, attaching
/var/tmp/portage/sys-libs/gdbm-1.8.3-r4/temp/build.log
as well
Thank you
--
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-amd64] Failure updating to gdbm-1.8.3-r4
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
1 sibling, 1 reply; 5+ messages in thread
From: James Ausmus @ 2010-01-18 20:44 UTC (permalink / raw
To: gentoo-amd64
[-- Attachment #1: Type: text/plain, Size: 523 bytes --]
On Mon, Jan 18, 2010 at 12:37 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.
Thanks!
-James
[-- Attachment #2: Type: text/html, Size: 1225 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-amd64] Failure updating to gdbm-1.8.3-r4
2010-01-18 20:44 ` James Ausmus
@ 2010-01-18 20:50 ` Daniel Dilts
2010-01-18 20:54 ` James Ausmus
0 siblings, 1 reply; 5+ messages in thread
From: Daniel Dilts @ 2010-01-18 20:50 UTC (permalink / raw
To: gentoo-amd64
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
> 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.
[-- Attachment #2: Type: text/html, Size: 2279 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-amd64] Failure updating to gdbm-1.8.3-r4
2010-01-18 20:50 ` Daniel Dilts
@ 2010-01-18 20:54 ` James Ausmus
0 siblings, 0 replies; 5+ messages in thread
From: James Ausmus @ 2010-01-18 20:54 UTC (permalink / raw
To: gentoo-amd64
[-- 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 --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-01-18 20:54 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox