From: Christian Thalinger <Christian.Thalinger@Sun.COM>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [patch] Fix Darwin breakage
Date: Thu, 20 Aug 2009 17:16:00 -0000 [thread overview]
Message-ID: <4A8D8311.8040806@Sun.COM> (raw)
In-Reply-To: <8ac60eac0908201001h4e0de16ev9e9a79ec40ec0de3@mail.gmail.com>
Paul Pluzhnikov wrote:
> On Thu, Aug 20, 2009 at 9:42 AM, Christian
> Thalinger<Christian.Thalinger@sun.com> wrote:
>
>> The problem is the size of the stuff you need:
>>
>> $ du -sc build/bsd/bsd_i486_compiler2/ build/bsd/jdk-bsd-i586/
>> 1308012 total
>
> Is that in blocks of 512B, or blocks of 1KB?
It's 512B blocks:
$ du -sch build/bsd/bsd_i486_compiler2/ build/bsd/jdk-bsd-i586/
275M build/bsd/bsd_i486_compiler2/
364M build/bsd/jdk-bsd-i586/
639M total
>
> I think we can arrange to transfer a 1GB file (it will likely compress
> reasonably well), though it may be easiest for me to just drive to Santa
> Clara and pick up a CD or DVD (if you are in fact in the bay area).
The drive would be long... I'm in Vienna, Austria :-)
>
>> I should try something smaller...
>
> Or I could try building jdk locally (are there many dependencies?)
It's not that complicated. I try a fresh build and if it's fairly easy,
I send you the instructions.
-- Christian
next prev parent reply other threads:[~2009-08-20 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 16:32 Paul Pluzhnikov
2009-08-14 17:56 ` Paul Pluzhnikov
2009-08-14 19:09 ` Tom Tromey
2009-08-14 18:32 ` Tom Tromey
2009-08-14 19:15 ` Paul Pluzhnikov
2009-08-18 12:24 ` Christian Thalinger
2009-08-18 16:17 ` Paul Pluzhnikov
2009-08-20 17:01 ` Christian Thalinger
2009-08-20 17:09 ` Paul Pluzhnikov
2009-08-20 17:16 ` Christian Thalinger [this message]
2009-08-21 11:30 ` Christian Thalinger
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=4A8D8311.8040806@Sun.COM \
--to=christian.thalinger@sun.com \
--cc=gdb-patches@sourceware.org \
--cc=ppluzhnikov@google.com \
/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