I have attempted to install several of these modules via CPAN, using every variation on make I can findWhy did you do that? You should only use what perl -MConfig die$Config{make} reports as your make tool. To attempt different ones would end in certain failure.
I spend a good deal of time compiling modules, and maintaining my own ppm repository.
CPAN.pm in my experience, has sucked enormously on win32 ~ CPANPLUS has faired better, but I still prefer to do things manually. The next release of CPANPLUS is highly anticipated, because it will essentially replace PPM (a great set of modules, but a very bad shell if you ask me).
Now, I checked out CGI::Panel, and it requires Apache::Session, MD5, and Storable, all of which you should either have, or are available over ppm. I get all my Apache/mod_perl modules fro Randy Kobes's ppm repository, including Apache::Session.
I suggest you update your CGI.pm ~ that way you can have at least 1 good install experience under your belt ;)
update: If you dont' have your enviroment set up right, you may have to run vcvars32.bat.
After a manual install, I also find it useful to run
perl -MActivePerl::DocTools -e ActivePerl::DocTools::UpdateHTML() perl -MActivePerl::DocTools -e ActivePerl::DocTools::WriteTOC()
Dog_and_pony: while that is true, I still need to run WriteToc sometimes, and well, I haven't typed the above snippet since I day I wrote it on my homenode (been cut'n'pasting ever since, and will continue to do so).
____________________________________________________
** The Third rule of perl club is a statement of fact: pod is sexy.
In reply to Re: nmake, CPAN and Modules not listed in PPM
by PodMaster
in thread nmake, CPAN and Modules not listed in PPM
by Flame
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |