Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:0

Bundle::Slash Woes?

posted by Krow on 07:06 AM September 17th, 2001   Printer-friendly   Email story
jitters writes "Love the code guys.. its great. But after a day i almost have it running.. One issue is this.. I am running RH 7.1 and had no problems through the whole install until i went to install the Bundle::Slash. All of it goes in except that when it gets to the Apache::Cookie(actually libapreq) it just dies.. and will not install. Read through the install guide many times and looked through the archives.. If anyone could offer up a suggestion it would be greatly appreciated. BTW this was a bare bone install following the install guide to the letter. Thanks much"
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login
Loading... please wait.
  • did you drop out of cpan and do the perl Makefile.PL && make && make test && make install from the shell?

    I just did an entire perl 5.6.1 install on a redhat7.1 box (I rpm -e'd perl first). It was the most problem-free install yet for me.
    lottadot []
  • Just installed the latest perl after finding an obscure article about installing 5.6.1 FIRST by hand then continuing on with the install. So far so good. Thanks for the help.
    We're on a mission from God.. Elwood Blues
  • Well still at the same spot! When Bundle::slash gets to libnet it wanks out on Net::telnet and Net::cmd.. if fails the t/require test??? If you have anysuggestions i am all ears! thanks
    We're on a mission from God.. Elwood Blues
    • You can ignore the Net::Telnet test failure I think as slash doesn't seem to need it. I have a box without telnet (just ssh) and so Net::Telnet wouldn't pass its test. You can go into the t directory of that module and remove the tests (or preferably edit it out). Dunno about Net::cmd though looking at perldoc Net::cmd it looks like you need it.
      -- SF and Computing Book News