id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,lang,patch,platform
2116,t/library/nciutils.t fails on a plain parrot,dukeleto,jkeenan,"{{{
$ prove -v t/library/nciutils.t 
t/library/nciutils.t .. 
1..13
ok 1 - load_bytecode
No NCI thunk available for signature `ptr (ptr, STRING)'
current instr.: 'parrot;NCI;Utils;nciwrap' pc 558 (runtime/parrot/library/NCI/Utils.pir:421)
called from Sub 'main' pc 87 (t/library/nciutils.t:49)
Dubious, test returned 1 (wstat 256, 0x100)
Failed 12/13 subtests 

Test Summary Report
-------------------
t/library/nciutils.t (Wstat: 256 Tests: 1 Failed: 0)
  Non-zero exit status: 1
  Parse errors: Bad plan.  You planned 13 tests but ran 1.
Files=1, Tests=1,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.00 cusr  0.01 csys =  0.03 CPU)
Result: FAIL
}}}

This is most likely because my ""plain parrot"" script disables everything, including extra nci thunks: 
{{{
$ cat /home/leto/bin/new_parrot_plain 
#!/bin/sh

new_parrot --without-gettext  --without-gmp --without-libffi \
            --without-extra-nci-thunks \
           --without-opengl --without-readline               \
           --without-pcre --without-zlib                     \
           --without-threads --without-icu $@
}}}

It is not clear to me how to detect if we have those from our tests.",bug,closed,normal,,testing,3.4.0,medium,fixed,,ligne,,,all