#610: cross-compile configuration
-----------------------+----------------------------------------------------
Reporter: allison | Owner: dukeleto
Type: roadmap | Status: assigned
Priority: normal | Milestone: 2.6
Component: configure | Version:
Severity: medium | Keywords:
Lang: | Patch:
Platform: all |
-----------------------+----------------------------------------------------
Comment(by darbelo):
Replying to [comment:5 jkeenan]:
> > We've had file-based configuration available (`perldoc Configure.pl`)
for several years now. What else might we need to reach the objective of
this ticket.
> >
>
> Perhaps I should have put that in the form of a question: What else
might we need to reach the objective of this ticket?
IIRC, from my experimentation with this last year, file based
configuration proved to be sufficient to start building parrot, the
problem is that this only concerns the parts of parrot that are written in
C. We can cross-compile those fine, mostly, but then we run into build
steps that attempt to run code that has just been built (like, say, the
miniparrot executable) for a different architecture, with predictable
failure. My guess is that the Configure side of things is fine as is, and
the remaining issues should be adressed in the build process proper.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/610#comment:6>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
