----- Original Message ----- From: "Chris Marshall" <[EMAIL PROTECTED]> . . >> >> inlinepdlpp is the Gorilla problem. All OSes tested with >> perls 5.8.x or 5.10.0 fail on this one! Debugging help >> welcomed. I have never seen an error with autoload or >> inlinepdlpp on cygwin. I'll try a clean test tonight. >>
I have one explanation - if the Inline directory (where Inline builds its stuff) already has a config file, then instead of writing a new config file, Inline just uses the existing one - and if that existing config file doesn't mention Pdlpp (and it won't mention Pdlpp) then Inline stops with the error message we're seeing. If there's no existing config file in the Inline directory, then Inline first creates one - and includes in that file every inline language that is being supported (which will include Pdlpp). By deleting the existing config file and then re-running the app (as per the recommendation of the error message), we force Inline to write a new config file (one that will include Pdlpp) and all is sweet. If the testers were to use a fresh Inline directory (one that doesn't already contain an Inline config file), there would be no problem .... but I don't know how to force that to happen. Another solution might be to have inlinepdlpp.t first delete any exisiting config file in the Inline directory. I don't know if that can be done, and I don't know how it would be recieved. As to the fact that there's no such problem with 5.6.2 .... I can only assume that the Inline directory being used for that version of perl (which is a separate directory to the ones being used for 5.8 and 5.10) doesn't contain a pre-existing config file. We really need to ask one of the testers about this - just to confirm what's going on, and to find out how we can have a fresh "Inline directory" used for PDL testing. Cheers, Rob _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
