#1890: installed parrot requires build dir.
---------------------+------------------------------------------------------
 Reporter:  coke     |       Owner:  jkeenan 
     Type:  bug      |      Status:  assigned
 Priority:  normal   |   Milestone:  2.11    
Component:  install  |     Version:  2.10.0  
 Severity:  medium   |    Keywords:          
     Lang:           |       Patch:          
 Platform:  darwin   |  
---------------------+------------------------------------------------------
Changes (by jkeenan):

 * cc: doughera, allison, tommyd, JadeNB (added)
  * owner:  => jkeenan
  * status:  new => assigned


Comment:

 Replying to [comment:2 jkeenan]:
 > 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?
 >

 On Darwin, I configured with a `--prefix` directory and subsequently
 called `make install`.  I then followed the instructions in
 ''tools/dev/mk_language_shell.pl'' for creating a new language
 implementation:
 {{{
 $> perl tools/dev/mk_language_shell.pl Xyz
 $> cd xyz
 }}}
 Using, in turn, each of the installed parrot and the build-directory
 parrot, I then called:
 {{{
 $> parrot setup.pir
 $> parrot setup.pir test
 }}}
 In each case, the language built and tested satisfactorily.  I also ran
 ''mk_language_shell.pl'', changed the name of the build directory, and ran
 the setup.pir commands with the installed executable.  Again, the results
 were satisfactory.

 I infer from this that the test failure in ''t/tools/mk_language_shell.t''
 I experienced earlier when configuring with my patch to
 ''config/init/hints/darwin.pm'' is a problem with the test file -- not a
 problem with the patch or with ''tools/dev/mk_language_shell.pl''.

 Other opinions?  Am cc-ing contributors to TT #344.

 Thank you very much.

 kid51

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/1890#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to