#1890: installed parrot requires build dir.
---------------------+------------------------------------------------------
Reporter: coke | Owner:
Type: bug | Status: new
Priority: normal | Milestone: 2.11
Component: install | Version: 2.10.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: darwin |
---------------------+------------------------------------------------------
Changes (by jkeenan):
* platform: => darwin
* component: none => install
Comment:
1. This appears to be much the same issue discussed in TT #344.
2. moritz++ pointed out that Rakudo's RT #76808 apparently refers to the
same problem.
3. I have attached a patch which, AFAICT, enables me to build and install
Parrot, run `make clean` on the build directory (my sandbox), and then
have all the installed executables work. ('work' in the sense of, I can
call the executable with `--version`, `--help`, etc., get expected output
and not get warnings or failure messages.)
But this comes at a cost. Before I installed, when I ran `make test` in
the build dir (as I customarily do), I got these failures in
''t/tools/mk_language_shell.t'':
{{{
[parrot] 542 $ prove -v t/tools/mk_language_shell.t
t/tools/mk_language_shell.t ..
1..7
ok 1 - mk_language_shell basic sanity
ok 2 - test_parrot_language_25310 dir exists
ok 3 - test_parrot_language_25310/t dir exists
ok 4 - test_parrot_language_25310/src dir exists
ok 5 - test_parrot_language_25310/setup.pir exists and has nonzero size
not ok 6 - language builds, exit code = 133
# Failed test 'language builds, exit code = 133'
# at t/tools/mk_language_shell.t line 60.
not ok 7 - language passes all tests, exit code = 133
# Failed test 'language passes all tests, exit code = 133'
# at t/tools/mk_language_shell.t line 65.
# Looks like you failed 2 tests of 7.
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/7 subtests
Test Summary Report
-------------------
t/tools/mk_language_shell.t (Wstat: 512 Tests: 7 Failed: 2)
Failed tests: 6-7
Non-zero exit status: 2
Files=1, Tests=7, 2 wallclock secs ( 0.10 usr 0.04 sys + 0.44 cusr
0.15 csys = 0.73 CPU)
Result: FAIL
}}}
Until today I never looked at this test before, and I have never used the
program it calls, ''tools/dev/mk_language_shell.pl'', before.
So I can't tell whether this indicates a serious problem with my patch or
whether it's a side effect of the way that program and its corresponding
test file are written. Does it make sense to try to create a new language
on top of a Parrot in the build directory as opposed to an installed
Parrot?
Note: I'm working on Darwin/PPC, so this is purely a Darwin issue -- not a
PPC vs Intel issue.
Thank you very much.
kid51
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1890#comment:2>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
