From: Justin <justin@j-schmitz.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] scons build failure
Date: Tue, 21 Oct 2008 09:21:47 +0200 [thread overview]
Message-ID: <48FD830B.10602@j-schmitz.net> (raw)
In-Reply-To: <5bdc1c8b0810201820p1ca163b7re5099f72863c0b34@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
Mark Knecht schrieb:
> Anything I should try to do about this?
>
> Thanks,
> Mark
>
> Saving to: `/usr/portage/distfiles/scons-1.0.0.tar.gz'
>
> 100%[======================================>] 541,330 682K/s in 0.8s
>
> 2008-10-20 18:18:02 (682 KB/s) -
> `/usr/portage/distfiles/scons-1.0.0.tar.gz' saved [541330/541330]
>
> * checking ebuild checksums ;-) ... [ ok ]
> * checking auxfile checksums ;-) ... [ ok ]
> * checking miscfile checksums ;-) ... [ ok ]
> * checking scons-1.0.0.tar.gz ;-) ... [ ok ]
>
>>>> Unpacking source...
>>>> Unpacking scons-1.0.0.tar.gz to /var/tmp/portage/dev-util/scons-1.0.0/work
>>>> Source unpacked.
>>>>
> * The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
> * is known to be triggered by things such as failed variable assignments
> * (bug #190128) or bad substitution errors (bug #200313).
>
> * Messages for package dev-util/scons-1.0.0:
>
> * The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
> * is known to be triggered by things such as failed variable assignments
> * (bug #190128) or bad substitution errors (bug #200313).
> lightning ~ #
>
>
On my system it works. Do you have enough space in /var/tmp/portage?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2008-10-21 7:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 1:20 [gentoo-amd64] scons build failure Mark Knecht
2008-10-21 7:21 ` Justin [this message]
2008-10-22 0:33 ` Mark Knecht
2008-10-22 3:19 ` Mark Knecht
2008-10-21 8:50 ` [gentoo-amd64] " Duncan
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=48FD830B.10602@j-schmitz.net \
--to=justin@j-schmitz.net \
--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