Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 87 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       This document describes various features of IBM's Unix
       operating system (AIX) that will affect how Perl version 5
       (hereafter just Perl) is compiled and/or runs.

       Compiling Perl 5 on AIX

       When compiling Perl, you must use an ANSI C compiler. AIX
       does not ship an ANSI compliant C-compiler with AIX by
       default, but binary builds of gcc for AIX are widely

       At the moment of writing, AIX supports two different
       native C compilers, for which you have to pay: xlC and
       vac. If you decide to use either of these two (which is
       quite a lot easier than using gcc), be sure to upgrade to
       the latest available patch level. Currently:

           xlC.C or or or or
           vac.C  or or

       note that xlC has the OS version in the name as of version, so you will find xlC.C for AIX-5.0 as package

           xlC.aix50.rte or

       subversions are not the same `latest' on all OS versions.
       For example, the latest xlC-5 on aix41 is, while
       on aix43, it is

       Perl can be compiled with either IBM's ANSI C compiler or
       with gcc.  The former is recommended, as not only can it
       compile Perl with no difficulty, but also can take advan­
       tage of features listed later that require the use of IBM
       compiler-specific command-line flags.

       The IBM's compiler patch levels and have
       compiler optimization bugs that affect compiling perl.c
       and regcomp.c, respectively.  If Perl's configuration
       detects those compiler patch levels, optimization is
       turned off for the said source code files.  Upgrading to
       at least is recommended.

       If you decide to use gcc, make sure your installation is
       recent and complete, and be sure to read the Perl README
       file for more gcc-specific details. Please report any
       hoops you had to jump through to the development team.

       OS level

       Before installing the patches to the IBM C-compiler you
       need to know the level of patching for the Operating Sys­
       The same might happen to AIX 5.1 or other OS levels. As a
       side note, perl cannot be built without bos.adt.syscalls
       and bos.adt.libm installed

           # lslpp -l | egrep "syscalls|libm"
           bos.adt.libm  COMMITTED  Base Application Development
           bos.adt.syscalls  COMMITTED  System Calls Application

       Building Dynamic Extensions on AIX

       AIX supports dynamically loadable objects as well as
       shared libraries.  Shared libraries by convention end with
       the suffix .a, which is a bit misleading, as an archive
       can contain static as well as dynamic members.  For perl
       dynamically loaded objects we use the .so suffix also used
       on many other platforms.

       Note that starting from Perl 5.7.2 (and consequently
       5.8.0) and AIX 4.3 or newer Perl uses the AIX native
       dynamic loading interface in the so called runtime linking
       mode instead of the emulated interface that was used in
       Perl releases 5.6.1 and earlier or, for AIX releases 4.2
       and earlier.  This change does break backward compatibil­
       ity with compiled modules from earlier perl releases.  The
       change was made to make Perl more compliant with other
       applications like Apache/mod_perl which are using the AIX
       native interface. This change also enables the use of C++
       code with static constructors and destructors in perl
       extensions, which was not possible using the emulated

       The IBM ANSI C Compiler

       All defaults for Configure can be used.

       If you've chosen to use vac 4, be sure to run
       Older versions will turn up nasty later on. For vac 5 be
       sure to run at least, but vac or up is
       highly recommended. Note that since IBM has removed vac through from the software depot, these
       versions should be considered obsolete.

       Here's a brief lead of how to upgrade the compiler to the
       latest level.  Of course this is subject to changes.  You
       can only upgrade versions from ftp-available updates if
       the first three digit groups are the same (in where you
       can skip intermediate unlike the patches in the developer
       snapshots of perl), or to one version up where the `base'
       is available.  In other words, the AIX compiler patches
       are cumulative.

        ftp> cd /aix/fixes/v4/
        ftp> dir other other.ll
        output to local-file: other.ll? y
        200 PORT command successful.
        150 Opening ASCII mode data connection for /bin/ls.
        226 Transfer complete.
        ftp> dir xlc xlc.ll
        output to local-file: xlc.ll? y
        200 PORT command successful.
        150 Opening ASCII mode data connection for /bin/ls.
        226 Transfer complete.
        ftp> bye
        ... goodbye messages
        # ls -l *.ll
        -rw-rw-rw-   1 merijn   system    1169432 Nov  2 17:29 other.ll
        -rw-rw-rw-   1 merijn   system      29170 Nov  2 17:29 xlc.ll

       On AIX 4.2 using xlC, we continue:

        # lslpp -l | fgrep 'xlC.C '
          xlC.C             COMMITTED  C for AIX Compiler
          xlC.C             COMMITTED  C for AIX Compiler
        # grep 'xlC.C.3.1.4.*.bff' xlc.ll
        -rw-r--r--   1 45776101 1        6286336 Jul 22 1996  xlC.C.
        -rw-rw-r--   1 45776101 1        6173696 Aug 24 1998  xlC.C.
        -rw-r--r--   1 45776101 1        6319104 Aug 14 1996  xlC.C.
        -rw-r--r--   1 45776101 1        6316032 Oct 21 1996  xlC.C.
        -rw-r--r--   1 45776101 1        6315008 Dec 20 1996  xlC.C.
        -rw-rw-r--   1 45776101 1        6178816 Mar 28 1997  xlC.C.
        -rw-rw-r--   1 45776101 1        6188032 May 22 1997  xlC.C.
        -rw-rw-r--   1 45776101 1        6191104 Sep  5 1997  xlC.C.
        -rw-rw-r--   1 45776101 1        6185984 Jan 13 1998  xlC.C.
        -rw-rw-r--   1 45776101 1        6169600 May 27 1998  xlC.C.
        # wget ftp://ftp.software.ibm.com/aix/fixes/v4/xlc/xlC.C.

       On AIX 4.3 using vac, we continue:

        # lslpp -l | grep 'vac.C '
         vac.C              COMMITTED  C for AIX Compiler
         vac.C              COMMITTED  C for AIX Compiler
        # grep 'vac.C.5.0.2.*.bff' other.ll
        -rw-rw-r--   1 45776101 1        13592576 Apr 16 2001  vac.C.
        -rw-rw-r--   1 45776101 1        14133248 Apr  9 2002  vac.C.
        -rw-rw-r--   1 45776101 1        14173184 May 20 2002  vac.C.
        -rw-rw-r--   1 45776101 1        14192640 Nov 22 2002  vac.C.
        # wget ftp://ftp.software.ibm.com/aix/fixes/v4/other/vac.C.

       Likewise on all other OS levels. Then execute the follow­
       ing command, and fill in its choices

       If linking miniperl

        cc -o miniperl ... miniperlmain.o opmini.o perl.o ... -lm -lc ...

       causes error like this

        ld: 0711-317 ERROR: Undefined symbol: .aintl
        ld: 0711-317 ERROR: Undefined symbol: .copysignl
        ld: 0711-317 ERROR: Undefined symbol: .syscall
        ld: 0711-317 ERROR: Undefined symbol: .eaccess
        ld: 0711-317 ERROR: Undefined symbol: .setresuid
        ld: 0711-317 ERROR: Undefined symbol: .setresgid
        ld: 0711-317 ERROR: Undefined symbol: .setproctitle
        ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information.

       you could retry with

        make realclean
        rm config.sh
        ./Configure -Dusenm ...

       which makes Configure to use the "nm" tool when scanning
       for library symbols, which usually is not done in AIX.

       Related to this, you probably should not use the "-r"
       option of Configure in AIX, because that affects of how
       the "nm" tool is used.

       Using GNU's gcc for building perl

       Using gcc-3.x (tested with 3.0.4, 3.1, and 3.2) now works
       out of the box, as do recent gcc-2.9 builds available
       directly from IBM as part of their Linux compatibility
       packages, available here:


       Using Large Files with Perl

       Should yield no problems.

       Threaded Perl

       Threads seem to work OK, though at the moment not all
       tests pass when threads are used in combination with 64bit

       You may get a warning when doing a threaded build:

         "pp_sys.c", line 4640.39: 1506-280 (W) Function argument assignment between types "unsigned char*" and "const void*" is not allowed.

       expect 64bit configurations to work. In combination with
       threads some tests might still fail.

       AIX 4.2 and extensions using C++ with statics

       In AIX 4.2 Perl extensions that use C++ functions that use
       statics may have problems in that the statics are not get­
       ting initialized.  In newer AIX releases this has been
       solved by linking Perl with the libC_r library, but unfor­
       tunately in AIX 4.2 the said library has an obscure bug
       where the various functions related to time (such as
       time() and gettimeofday()) return broken values, and
       therefore in AIX 4.2 Perl is not linked against the


       H.Merijn Brand <h.m.brand@hccnet.nl>


       Version 0.0.6: 23 Dec 2002

perl v5.8.1                 2003-09-02                 PERLAIX(1)

An undefined database error occurred. SELECT distinct pages.pagepath,pages.pageid FROM pages, page2command WHERE pages.pageid = page2command.pageid AND commandid =




Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial welcomes your suggestions and ideas.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.08 Seconds