Am 06.12.2011 11:19, schrieb Vasily Chekalkin:
On Tue, Dec 6, 2011 at 9:16 PM, Moritz Lenz<[email protected]> wrote:
Why should I? What's the policy for dynop vs. op? Does it make a difference?
If the logic for checking is inside some parrot source files included in
some core files, why should I have to load a dynop to access that
functionality?
Fair enough.
Then step-by-step build instruction:
1. make
2. apply patch
3. make bootstrap-ops (ignoring crash)
4. make reconfig
5. make
There is some missing dependencies causing crash. You can avoid it by
invoking "./ops2c --core" instead of step 3.
Thanks.
One more thing, should I put generated files and hand-edited changes
into separate commits?
And yes, tests are welcome with patch :)
Sure thing :-)
Cheers,
Moritz
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
