Re: Problems with instalation of XML::Parser 2.30
Hi Nikola, >From Indigostar's home page: Quote Installing CPAN modules requires that you have Microsoft DevStudio or nmake.exe installed. If you are installing modules that contain xs files, then you need DevStudio, otherwise you only need nmake.exe. End Quote. XML::Parser contains an xs file. Try compiling it with DevStudio. Good luck. Cheers, Rob Visit our website at http://www.kalinabears.com.au - Original Message - From: Nikola Knezevic <[EMAIL PROTECTED]> To: David LaPointe <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, February 05, 2001 6:57 AM Subject: Re: Problems with instalation of XML::Parser 2.30 > Dana 04.02.01, David LaPointe napisa: > > > If the goal is to just get PPM fixed, there may be a faster way to do that. > > Why not just try using the MSI installer to uninstall Perl and then > > re-install it? I've done that a couple of times in the last couple of weeks, > > and it seems to work pretty well. Back up your C:\Perl\site\lib\ppm.xml so > > you won't loose the list of installed modules, but otherwise it should be > > O.K. See if that repairs the problem. If it works, it will have been a lot > > faster than trying to wade through all those compiler errors. No? > > Nope, First of all, I'm using Perl 5.005. Second of all, there are many > modules installed 'by hand', without using ppm, but they were without c > parts. Third of all, I'm on 486 (yeees, that exists), so, any reinstalling > would be very painfull and lasting operation. > But, thanks for suggestion. > > My goal is to find why @@@!#!!$%!$ expat won't compile, and how to do that > kind (with c parts) of module installation by hand. > > -- > ... Dete je naslo kutiju sibica. I bi svetlost! > > - --- -- ---=- --==---===-[Nikola Knezevic]---===+ > +- -=- -==--=- -=-- --- -- - http://users.hemo.net/indy --- -- - > > > ___ > Perl-Win32-Users mailing list > [EMAIL PROTECTED] > http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users ___ Perl-Win32-Users mailing list [EMAIL PROTECTED] http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users
Re: Problems with instalation of XML::Parser 2.30
Dana 04.02.01, David LaPointe napisa: > If the goal is to just get PPM fixed, there may be a faster way to do that. > Why not just try using the MSI installer to uninstall Perl and then > re-install it? I've done that a couple of times in the last couple of weeks, > and it seems to work pretty well. Back up your C:\Perl\site\lib\ppm.xml so > you won't loose the list of installed modules, but otherwise it should be > O.K. See if that repairs the problem. If it works, it will have been a lot > faster than trying to wade through all those compiler errors. No? Nope, First of all, I'm using Perl 5.005. Second of all, there are many modules installed 'by hand', without using ppm, but they were without c parts. Third of all, I'm on 486 (yeees, that exists), so, any reinstalling would be very painfull and lasting operation. But, thanks for suggestion. My goal is to find why @@@!#!!$%!$ expat won't compile, and how to do that kind (with c parts) of module installation by hand. -- ... Dete je naslo kutiju sibica. I bi svetlost! - --- -- ---=- --==---===-[Nikola Knezevic]---===+ +- -=- -==--=- -=-- --- -- - http://users.hemo.net/indy --- -- - ___ Perl-Win32-Users mailing list [EMAIL PROTECTED] http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users
Re: Problems with instalation of XML::Parser 2.30
What's the goal here? Nikola Knezevic wrote: > Hi, > I was little curious, so I tried to install XML::Parser 2.30 without > using PPM - by using classic UNIX metod: unpack, make, make install, > etc... > Everything started fine,..., and then my nightmare started. If you want to learn how to wade through the errors and get it to work by hand, fine. That might be fun, and it would probably be interesting. But it sounds like a lot of work. If the goal is to just get PPM fixed, there may be a faster way to do that. Why not just try using the MSI installer to uninstall Perl and then re-install it? I've done that a couple of times in the last couple of weeks, and it seems to work pretty well. Back up your C:\Perl\site\lib\ppm.xml so you won't loose the list of installed modules, but otherwise it should be O.K. See if that repairs the problem. If it works, it will have been a lot faster than trying to wade through all those compiler errors. No? Dave LaPointe ___ Perl-Win32-Users mailing list [EMAIL PROTECTED] http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users
