>>>>> "JH" == Jarkko Hietaniemi <[EMAIL PROTECTED]> writes:
JH> An OS problem and a build environment (cross-compilation, yuk)
JH> problem. I once managed to compile miniperl (5.005) for Chorus.
JH> I'm about to unearth the cross-compilation changes I had to make to
JH> get that working. (You thought Configure was hairy enough already?
JH> Think again: the test executables have transfered to and run on the
JH> I forgot: also the input files need to transferred to the target.
try porting a BSD 4.1 kernel and utils to a prototype cpu card, all over
a single serial line. this started with burning roms! :)
JH> I think there are true limits imposed by the more limited CPUs
JH> like address space. I think there might be nasty assumptions one
JH> easily makes that work only on 32-bit or more address spaces.
well, i said that too. most (by volume shipped) real world embedded
controllers are dinky and inside your microwave, etc. they are meant to
be as cheap as possible, and have minimal ram/rom. perl is not possible
on them at all. the larger ones which run a proper RTOS could be
targeted for perl. so my point was that if the RTOS was decent/powerful
enough, perl should be able to be ported. hence qnx supporting it so
easily, but vxworks is not fully done. some combinations of RTOS and cpu
may be trickier or impossible. we can make perl6 work out of the box for
vxworks for many chips IMO. we just have to keep it modular and trim for
these platforms.
uri
--
Uri Guttman --------- [EMAIL PROTECTED] ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
