in reply to LWP Autoload problem?

What happened during "make test" on the installation? Did you install using CPAN.pm? Did you install all the necessary prerequisites?

-- Randal L. Schwartz, Perl hacker

Replies are listed 'Best First'.
Re: Re: LWP Autoload problem?
by nabeshin (Initiate) on Oct 15, 2001 at 20:31 UTC
    I installed from a tarball snagged via http://search.cpan.org/...

    "make test" goes through okay with the exception of some complaints about IO::Socket::INET symbol duplicates (see prior reply).

    Another (possibly) interesting note: there isn't a "blocking.al" file within the LWP distribution tarball.

    What exactly is a .al file, anyways? :P
      "make test" goes through okay with the exception of some complaints about IO::Socket::INET symbol duplicates (see prior reply).
      That means your IO::Socket module is out of date. Did you also install all of the prerequisites, ensuring they were up to date?
      Another (possibly) interesting note: there isn't a "blocking.al" file within the LWP distribution tarball.
      Right, it gets created during the "make all", because it's an autoloaded module.

      -- Randal L. Schwartz, Perl hacker

        even after performing a "make all" there was no such file... all of the prerequisites were up to date.

        as far as IO::Socket, I have it as part of the base perl install... if it were my decision, I'd test 5.6.1 against our existing code, but alas, it is not my decision to make... and since any changes to the existing system must be done within the packaging system, I can't do CPAN updates. :\
Re: Re: LWP Autoload problem?
by nabeshin (Initiate) on Oct 15, 2001 at 20:11 UTC
    I do have another issue of which I'm aware:

    IO::Socket::INET is defined in <perl modules>/$ARCH/IO/Socket.pm

    LWP uses IO::Socket::INET explicitly in a few places (e.g. "use IO::Socket::INET;"), so this introduces a little conundrum. Perl looks for what it expects (<perl modules>/$ARCH/IO/Socket/INET.pm), and failing that, bombs out. Now, altering the "use" statement to "use IO::Socket;" will fix the problem, but this isn't a good thing, since I have to deploy this on a number of machines. Another semi-fix is to create a symlink from <perl modules>/$ARCH/IO/Socket/INET.pm to <perl modules>/$ARCH/IO/Socket.pm this doesn't really help either, since it can cause duplicate references. *sigh*

    however, I currently use the symlink fix, which works in most instances.