[tahoe-dev] Tahoe-LAFS on Fedora 14

[Sameer Verma]

On Tue, Jun 26, 2012 at 2:13 AM, Sameer Verma <sverma at sfsu.edu> wrote:
> On Sun, Jun 24, 2012 at 8:47 PM, Sameer Verma <sverma at sfsu.edu> wrote:
>> On Sun, Jun 24, 2012 at 6:36 PM, Zooko Wilcox-O'Hearn <zooko at zooko.com> wrote:
>>> On Sun, Jun 24, 2012 at 2:18 PM, Sameer Verma <sverma at sfsu.edu> wrote:
>>>>
>>>> So, after a long break, I'm at it again.
>>>
>>> Welcome back!
>>>
>>>> {standard input}: Assembler messages:
>>>> {standard input}:217576: Error: open CFI at the end of file; missing
>>>> .cfi_endproc directive
>>>> gcc: Internal error: Killed (program cc1plus)
>>>> Please submit a full bug report.
>>>> See <http://bugzilla.redhat.com/bugzilla> for instructions.
>>>> error: Setup script exited with error: command 'gcc' failed with exit status 1
>>>
>>> Well, darn. My first guess is that it ran out of RAM and that this is
>>> what happens to gcc when one of its mallocs fails.
>>>
>>> Maybe try the build again and watch the memory usage?
>>>
>>> Perhaps a prebuilt binary package of pycryptopp would suffice. What's
>>> the output of:
>>>
>>> python -c 'import platform;print platform.platform(),platform.python_version()'
>>>
>>> Thanks!
>>>
>>
>> bash-4.1# python -c 'import platform;print
>> platform.platform(),platform.python_version()'
>> Linux-2.6.35.13_xo1-20120508.1133.olpc.eb0c7a8-i586-with-fedora-11-based_on_Fedora_14
>> 2.7.0
>>
>>
>>
>>> Oh, by the way, I still think it might be worth setting up an OLPC as
>>> a buildslave. Do you have a spare OLPC that you could dedicate to that
>>> task?
>>
>> I do have a spare OLPC XO-1 (with a broken screen - perfect!). Can you
>> briefly specify what this machine needs to have on it and how it will
>> talk to the network and for how long.
>>
>> cheers,
>> Sameer
>>
>>>
>>> Regards,
>>>
>>> Zooko
>>> _______________________________________________
>>> tahoe-dev mailing list
>>> tahoe-dev at tahoe-lafs.org
>>> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>>>
>>>
>
>
> After messing around with the size of /tmp and creating swapfiles, it
> occurred to me to do this on a OLPC XO 1.5, which is a x86 machine
> with 1GHz  CPU and 1GB RAM. I had to up the /tmp to 256MB from 50MB.
> It ran like a champ!
>
> I have a bin folder all ready to run. Will try this out tomorrow on
> XO-1 machines (AMD Geode CPU @ 433MHz w/ 256MB RAM). Let's see if it
> will fly.


So, the build runs fine on a XO 1.5. What should I be copying over to
the XO-1 machine?

cheers,
Sameer