[M3devel] ***SPAM*** RE: Linux/ARM? Android?

Jay K jay.krell at cornell.edu
Thu May 20 15:12:20 CEST 2010


If you can provide ssh access to it and a "native" C development environment, I'll have a go at it.
By "native" C development, I mean "official", not necessarily "hosted on the target machine".
If the C development environment is easily acquired, I can do that part. It probably is.
There's a possibility, possibility, we should have separate ARM_LINUX and ARM_ANROID or or ARM_GNU_LINUX or ARM_BIONIC_LINUX or ARM_LINUX_ANDROID or ARM_LINUX_GOOGLE or ARM_GOOGLE or ARM_LINUX_GOOGLE or ARM_GOOGLE_LINUX or ARM_OHSA_LINUX ("open handset aliance?") or such.


In particular, if there jmpbuf sizes are different, then we should.
The "Modula-3 compiler" cares only about: endian, word size, jmpbuf size, basically that's it.
 Alignment too, but they are all the same.
 "Code alignment" too, some of each, for the closure stuff.


If they aren't binary compatible, then we probably should -- just to propagate it out to the naming of packages really.


There is "something" nagging to get out that isn't a "target" or  "platform" but something like a "configuration".
 For example, SOLsun and SOLgnu are the same, except for which C compiler they use to compiler a few files, and for the C-compiler-as-linker-driver.
  They have the same jumpbuf, the same stack walker, they end up with the same #ifs in the C code, at least wrt #if __sun, not #if __GNUC__.


Basically it seems that "platform" = "kernel" + "C library" + processor + "sometimes C compiler/linker" + "Windowing system" + "GUI library" + "file i/o library"
But many of them correlate very very strongly.
"C library" varies -- uclibc, dietlibc, glibc, eglibc, bionic.
file i/o library = posix or win32
threads = pthreads or posix user threads perhaps or win32
   (ie: we should have separate I386_LINUX_USERTHREADS?)


 - Jay

----------------------------------------
> From: dragisha at m3w.org
> To: jay.krell at cornell.edu
> Date: Thu, 20 May 2010 14:24:32 +0200
> CC: m3devel at elegosoft.com
> Subject: Re: [M3devel] ***SPAM*** RE: Linux/ARM? Android?
>
> I'll have a HTC Tattoo in a week or so. No problems then for anything.
>
> It does not support pthread_cancel, as far as I know for now. And I
> don't think we need it. Nor glibc - it's lib is bionic (didn't check it
> yet).
>
> On Thu, 2010-05-20 at 11:47 +0000, Jay K wrote:
>> Status is roughly nowhere.
>> Chances are not bad though.
>> There is very little work to do when the system supports posix and gcc supports the system, and that describes a lot of systems.
>> Try this: cd scripts/python && ./boot1.py ARM_LINUX
>>
>>
>> Give me ssh access to a device?
>> Or maybe there is emulator?
>>
>>
>> I've had a PogoPlug (Linux/ARM) for over a year, haven't touched it.
>> And some I think Linux/ARM LaCie network drive also.
>>
>>
>> - Jay
>>
>> ----------------------------------------
>>> From: dragisha at m3w.org
>>> To: m3devel at elegosoft.com
>>> Date: Thu, 20 May 2010 12:08:53 +0200
>>> Subject: [M3devel] Linux/ARM? Android?
>>>
>>> As per subject... What is status of Linux/ARM port of Modula-3 and
>>> chances for Android port?
>>> --
>>> Dragiša Durić
>>>
>>
>
> --
> Dragiša Durić 
>
 		 	   		  


More information about the M3devel mailing list