From: sean darcy <seandarcy@hotmail.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: piggy broken in 2.5.24 build
Date: Sat, 22 Jun 2002 21:32:03 -0400 [thread overview]
Message-ID: <3D152513.8010801@hotmail.com> (raw)
In-Reply-To: linux.kernel.Pine.LNX.4.44.0206221501430.7338-100000@chaos.physics.uiowa.edu
Kai Germaschewski wrote:
> On Sat, 22 Jun 2002, sean darcy wrote:
>
>
>>At the end of make bzImage I get:
>>
...................
> So the question is why does the objcopy ... line not generate the tmp_xx
> file. I don't see it spitting out any error either, but could you check
> the obvious, like remaining free space on that filesystem and /tmp?
>
........................
> --Kai
>
20 gigs free. Aren't these big new disks great?
Glad it's not a build problem. Just wish I could figure out what kind of
problem it is.
jay
next parent reply other threads:[~2002-06-23 1:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <linux.kernel.Pine.LNX.4.44.0206221501430.7338-100000@chaos.physics.uiowa.edu>
2002-06-23 1:32 ` sean darcy [this message]
2002-06-23 1:35 ` piggy broken in 2.5.24 build Larry McVoy
2002-06-23 2:46 ` Kai Germaschewski
[not found] <linux.kernel.Pine.LNX.4.44.0206222143550.7338-100000@chaos.physics.uiowa.edu>
2002-06-23 16:03 ` sean darcy
[not found] <linux.kernel.20020623095429.A5667@mars.ravnborg.org>
2002-06-23 15:27 ` sean darcy
[not found] <linux.kernel.20020622213422.A13652@mars.ravnborg.org>
2002-06-23 1:22 ` sean darcy
2002-06-23 7:54 ` Sam Ravnborg
2002-06-22 17:41 sean darcy
2002-06-22 19:34 ` Sam Ravnborg
2002-06-22 20:07 ` Kai Germaschewski
2002-06-22 20:52 ` Diego Calleja
2002-06-22 21:08 ` Kai Germaschewski
2002-06-22 21:35 ` Diego Calleja
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=3D152513.8010801@hotmail.com \
--to=seandarcy@hotmail.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.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