use Perl

• Compiler and linker? (Score:2)

  by jdavidb (1361)

  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 t

  --
  J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
  • Re:Compiler and linker? (Score:1)

    by bluto (225)

    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.
    • Re:Compiler and linker? (Score:2)

      by jdavidb (1361)

      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
      • Re:Compiler and linker? (Score:2)

        by gabor (1626)

        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

        --
        

        • Test automation using Perl [szabgab.com]
        • Re:Compiler and linker? (Score:1)

          by n1vux (1492)

          Be aware that xlC and xlc are two different compilers (or rather, sets of options) on AIX.

          --
          Bill
          # I had a sig when sigs were cool
          use Sig;
          • Re:Compiler and linker? (Score:2)

            by gabor (1626)

            lovely

            thanks for the warning, next time I am there I should look into this more closely

            --
            

            • Test automation using Perl [szabgab.com]
• My two cents (Score:1)

  by runrig (3385)

  I've built perl 5.6.1 on AIX, using xlc, though perl -V will say 'cc' since 'cc' is just a link to 'xlc'(/usr/lpp/xlC/xlC). It's interesting that your linker also says 'xlc', because mine says 'ld' (/usr/ccs/bin/ld). I haven't had trouble building most modules, the only problem I remember is with anything that needs libiconv.
• ^M (Score:2)

  by bart (450)

  What are all those CR characters, marked by "^M" at the end of each line, in your text? That smells as if it's been poorly transported from a Windows platform, to yours.