#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 doughera):
Replying to [comment:5 jkeenan]:
> Please do a checkout of the ''gcc_defines'' branch from Subversion and
configure on the machine where you have RTEMS. Then call `grep -i
gccdefines__rtems__ lib/Parrot/Config/Generated.pm config_lib.pir`. Then
tell me if you can take it from there.
I'm unsure if this will be useful. For comparison, perl 5's Configure
also attempts to figure out the symbols #defined for the the current C
preprocessor. It's over 200 lines of shell code, running from line 21,467
to 21,687 in Configure. The output is stored in $Config{cppsymbols}. As
far as I know, the output is no longer ever used.
Within C code, if you want to check {{{#ifdef __rtems__}}}, you simply do
so. You don't need any Configure probe. Outside of C code, I agree you
need to run some kind of probe, but this looks overly complicated to me.
As I have mentioned previously in this ticket, I think the osname probe is
the more natural place to do this.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1840#comment:6>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
