#1840: Config step to detect RTEMS
-----------------------+----------------------------------------------------
Reporter: dukeleto | Owner: jkeenan
Type: feature | Status: assigned
Priority: normal | Milestone: 2.10
Component: configure | Version: 2.10.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
-----------------------+----------------------------------------------------
Comment(by jkeenan):
Replying to [comment:6 doughera]:
> Outside of C code, I agree you need to run some kind of probe ....
> [T]he osname probe is the more natural place to do this.
Andy,
Thanks for taking another look at this.
Here I'm bumping up against the limits of my understanding of the problem
we're trying to address in this ticket. Are we:
* checking to see whether the OS on which we are trying to configure and
build Parrot '''is''' RTEMS? If so, then I would ask dukeleto: ''What do
you get on your RTEMS box for `osname` in
''lib/Parrot/Config/Generated.pm''.
or:
* checking to determine whether the box on which we are working (and which
is presumably capable of compiling Parrot) is capable of (cross-)compiling
RTEMS?
kid51
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1840#comment:7>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
