----- Original Message ----- From: "Ira Woodhead" <[EMAIL PROTECTED]> To: <inline@perl.org> Sent: Saturday, January 21, 2006 5:33 AM Subject: (text-scan compile) FW: Help needed on Perl module, thanks a lot
I'm forwarding this exchange with a user. It looks like perhaps his setup is janky, but I don't know. Any advice appreciated, thanks! [snip] -------------------------------- I can't find any problem with Text::Scan-0.26 on any of my Win32 perls. I think he's probably using the free command line version of the Microsoft .NET compiler - which is not ideal (since it's not the compiler that was used to build ActiveState perl), but is not necessarily a problem. One shortcoming is that it's not an "all in one" download - Microsoft like to hide bits and pieces of it here and there, and it's quite easy to miss a crucial piece. I'd check first that he can build a normal extension - say Math::FFT from CPAN. (I usually specify that module because I know it is straightforward to compile, and because it also has no pre-requisites.) I find Inline::C failures can be tricky to diagnose - it's often far easier to identify the problem wrt the building of a "normal" extension. Feel free to have the OP cc me (and I'll include both of you in any replies I send) - but he probably shouldn't cc this list, as I don't think it's an Inline issue :-) ActiveState have (as of build 815) undertaken to have their builds of perl work seamlessly with the freely available MinGW (gcc) compiler. I would far prefer that Win32 users start using *that* compiler in preference to the free compiler that Microsoft are offering - MinGW is easier to install and offers better mileage. Cheers, Rob
