"RTEMS parrot runs, now what ?" (3 lines) at http://nopaste.snit.ch/18530
Joel Sherrill
joel.sherrill at oarcorp.com
Wed Nov 4 03:20:15 UTC 2009
Chris Johns wrote:
> Jonathan Leto wrote:
>
>> Howdy,
>>
>>
>>> Wow! This is real progress Chris. I go away for a couple of days and
>>> return
>>> to see this. :)
>>>
>>> Any news on the examples?
>>>
>>>
>> Chris and I are still trying to get parrot+rtems to actually open a
>> Parrot file and execute it, without segfaulting. It is possible that
>> parrot on rtems is attempting to use a unicode library (libicu) when
>> it shouldn't be:
>>
>> http://nopaste.snit.ch/18550
>>
>>
>
> We have RTEMS running ....
>
> http://nopaste.snit.ch/18553
>
>
Great job guys! How much of Parrot does this prove works?
What else needs to be done before the champagne is popped? :)
> It was a 64bit ABI vs 32bit ABI thing brought about by me configuring on
> a 64bit machine and then hacking for a 32bit machine.
>
>
So the issues are mainly around the configuration step? It looks
like it worked after you got over a couple of mismatches from Linux
to RTEMS.
> Many thanks to all who have helped get the port this far.
>
>
Indeed.
> Regards
> Chris
>
More information about the parrot-dev
mailing list