Hi!
* Alexander Schmehl <[EMAIL PROTECTED]> [061209 00:01]:
> Thanks for your interest. We are not sure yet, how long it will take to
> sort things out, but we will get back to you.
Note to myself: Don't send semi-automated responsed to lists /
discussion mails.
Sorry,
Alexander
signature
Hi!
Thanks for your interest. We are not sure yet, how long it will take to
sort things out, but we will get back to you.
Yours sincerely,
Alexander
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, Dec 06, 2006 at 12:57:11AM +0100, Joerg Jaspert wrote:
> On 10860 March 1977, Joerg Jaspert wrote:
>
> > So, if you want a machine from the following list, send a mail to
> > [EMAIL PROTECTED] and give a rough description what you plan to do with
> > it.
>
> Hihi, Update: Please notice th
please requeue gjdoc on m68k without any timeouts.
thanks, Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, Dec 04, 2006 at 07:46:55PM -0800, Rob Browning wrote:
>
> In the latest upload of stalin (a new version), I removed arm and m68k
> from the architecture list. However, I wanted to double-check and
> make sure that was appropriate.
>
> I believe compiling stalin with gcc now requires a bi
> > How do you get the peak VM usage data, then? That's been baffling me
> > since some time. Anyway, I'll give it a try one way or other.
>
> I didn't do anything very precise. I just watched the build (via top,
> htop, or proc -- I forget), and it looked like the virtual memory
> footprint went
Michael Schmitz <[EMAIL PROTECTED]> writes:
>> > Depending on the access pattern, a ratio of 2:1 swap to ram would be
>> > painful. The only machine where I could try that right away only has
>> > 256 MB RAM... and it's building gcc-snapshot right now.
>>
>> I don't really know how much RAM might
7 matches
Mail list logo
