Testing XS modules on Ponie

Arthur Bergman <[email protected]> writes:
>This is Ponie, development release 2
>------------------------------------
>
>	"And, isn't sanity really just a one-trick ponie anyway? I mean all 
>you get is one trick, rational thinking, but when you're good and 
>crazy, oooh, oooh, oooh, the sky is the limit." -- the tick
>
>
>Welcome to this second development release of ponie, the mix of perl5 
>and parrot. Ponie embeds a parrot interpreter inside perl5 and hands 
>off tasks to it, the goal of the project is to hand of all data and 
>bytecode handling to parrot.
>
>With this release all internal macros that poke at perl data types are 
>converted to be real C functions and to check if they are dealing with 
>traditional perl data types or PMC (Parrot data types) data. Perl 
>lvalues, arrays and hashes are also hidden inside PMCs but still access 
>their core data using traditional macros. The goal and purpose of this 
>release is to make sure this approach keeps on working with the XS 
>modules available on CPAN and to let people test with their own source 
>code. No changes where made to any of the core XS modules.

So ponie-2 compiles and passes all its tests for me.
So how do I see if it can handle the XS module from hell - Tk ?