Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • The configuration shows it was compiled by xlc, which I presume is AIX's proprietary C compiler. Are you using xlc to compile the modules? (Are you intending to use it, and are you verifying that Makefile.PL is indeed picking it up? Might need to CC=xlc Makefile.PL or modify your PATH.)

    Forgive me if this is stuff you already know. It might be something you've never heard of or thought of before, or it might be trivial old hat stuff to you. :)

    If you try to compile modules with a compiler other than that used to compile perl, your success is not guaranteed. I think it works sometimes on some platforms, but I would never depend on it. I always get gcc going and make sure to compile my own perl []. Have never used AIX; I might use the system compiler on that, if available, but I'd have more trust for gcc and definitely no trust if I was trying to mix output from the two.

    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
    • FWIW, I've never had luck on AIX with gcc, though that was generally years ago. Xlc or vac(?) tends to work ok, but you'll want to make sure they are reasonably up to date. That said, I 100% agree with the idea of building your own copy of perl. IBM's builtin perl is usually ancient and for some reason it causes me no end of grief when building/installing modules.
      • My advice is never, ever, ever, ever try to add a module to your OS vendor's version of perl. Compiler incompatiblities is the number one reason, along with inconsistent configuration options, possible behind-the-scenes changes your vendor made, and very importantly the chance that some user-level component of the operating system (say, sysadmin tools or init scripts) depends on an installed module that has changed in an incompatible way.

        It is near-trivial to install an independent perl for someone who i

        J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
        • Unfortunately I cannot make the people change the installed perl, I am totally dependent on some system administrators who told me to call the supplier of this module. They did not specify if I should call the maintainer of the module or CPAN...

          Anyway, this is perl supplied by IBM and installed in some way by the local sysadmins. As this is a productions system they don't let me install another perl that I'd compile.

          Both the compiler and the linker seem to be called XLC on this system