aixtoolbox-list — General discussion list for aixtoolbox

[tbox-l] Openssl

[<Sam...@in...>]

There is a Cert advisory out for some time now with a fix in openssl
0=2E9.7h and above. The openssl in the Toolbox has been 0.9.7g for some
time now. Is there anyway to get an update to a more recent level?

Thanks,

Sam


-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------

Re: [tbox-l] Request for new zlib - v1.2.3

[Reza A. <ar...@au...>]

Hi Ben,

On 15 Sep 2006, 04:35PM CDT, Benjamin Landman <la...@us...> wrote:
>       One of my customers in Austin requested a newer version of zlib to be
> made available on AIX 5.1 and higher. 

Funny you should bring that up.  We did just get permission to distribute
zlib-1.2.3, so you should see that updated in the Toolbox soon.

FYI, we did port all the security fixes mentioned on the zlib web site to the
zlib-1.2.2 package we currently have.


-- 
Reza Arbab
ar...@au...

[tbox-l] Request for new zlib - v1.2.3

[Benjamin L. <la...@us...>]

Greetings!
      One of my customers in Austin requested a newer version of zlib t=
o be
made available on AIX 5.1 and higher. Version 1.2.3 is available on the=

zlib web site and documents some important security fixes as well as bu=
g
fixes. My customer believes that there's an issue with v1.2.2 that impa=
cts
his ability to use compression through ssh using gzip and zlib. Any
thoughts on whether or not this new version could be built?

Thanks.
Ben

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Benjamin Landman
Manager - Dept F1XA -Software, Engineering Tools, Performance, and
Workstation Refresh
email: la...@us...     phone: (512)838-4590  (t/l 678-4590)=

[tbox-l] gdb useless for multithreaded (pthread) application

[Gabriel H. P. <pga...@rd...>]

Hi!

I have a problem with gdb crashing on AIX 5.2/32, 5.3/64 when trying to
debug 32 bit multithreaded applications.

The MT program works/runs fine as far as i can tell but i can not debug
it with either gdb 6.0 shipped in the aixtoolbox or with gdb 6.5 shipped
with PSDLIB.

Here is the test program I used:
========================  ptt.c ======================================
#include <pthread.h>
#include <stdio.h>

#define NUM_THREADS  3
#define TCOUNT 10
#define COUNT_LIMIT 12

int count = 0;
int thread_ids[3] = { 0, 1, 2 };
pthread_mutex_t count_mutex;
pthread_cond_t count_threshold_cv;

void *
inc_count (void *idp)
{
   int j, i;
   double result = 0.0;
   int *my_id = idp;

   for (i = 0; i < TCOUNT; i++)
   {
      pthread_mutex_lock (&count_mutex);
      count++;
[gabi@naomi:/home/gabi/swdev/pthread]
$ more ptt.c
#include <pthread.h>
#include <stdio.h>

#define NUM_THREADS  3
#define TCOUNT 10
#define COUNT_LIMIT 12

int count = 0;
int thread_ids[3] = { 0, 1, 2 };
pthread_mutex_t count_mutex;
pthread_cond_t count_threshold_cv;

void *
inc_count (void *idp)
{
   int j, i;
   double result = 0.0;
   int *my_id = idp;

   for (i = 0; i < TCOUNT; i++)
   {
      pthread_mutex_lock (&count_mutex);
      count++;

      /*
       * Check the value of count and signal waiting thread when
condition is
       * reached.  Note that this occurs while mutex is locked.
       */
      if (count == COUNT_LIMIT)
      {
         pthread_cond_signal (&count_threshold_cv);
         printf ("inc_count(): thread %d, count = %d  Threshold
reached.\n",
                 *my_id, count);
      }
      printf ("inc_count(): thread %d, count = %d, unlocking mutex\n",
              *my_id, count);
      pthread_mutex_unlock (&count_mutex);

      /* Do some work so threads can alternate on mutex lock */
      for (j = 0; j < 1000; j++)
         result = result + (double) random ();
   }
   pthread_exit (NULL);
}

void *
watch_count (void *idp)
{
   int *my_id = idp;

   printf ("Starting watch_count(): thread %d\n", *my_id);

   /*
    * Lock mutex and wait for signal.  Note that the pthread_cond_wait
    * routine will automatically and atomically unlock mutex while it
waits.
    * Also, note that if COUNT_LIMIT is reached before this routine is
run by
    * the waiting thread, the loop will be skipped to prevent
pthread_cond_wait
    * from never returning.
    */
   pthread_mutex_lock (&count_mutex);
   while (count < COUNT_LIMIT)
   {
      pthread_cond_wait (&count_threshold_cv, &count_mutex);
      printf ("watch_count(): thread %d Condition signal received.\n",
*my_id);
   }
   pthread_mutex_unlock (&count_mutex);
   pthread_exit (NULL);
}

int
main (int argc, char *argv[])
{
   int i, rc;
   pthread_t threads[3];
   pthread_attr_t attr;

   /* Initialize mutex and condition variable objects */
   pthread_mutex_init (&count_mutex, NULL);
   pthread_cond_init (&count_threshold_cv, NULL);

   /*
    * For portability, explicitly create threads in a joinable state
    * so that they can be joined later.
    */
   pthread_attr_init (&attr);
   pthread_attr_setdetachstate (&attr, PTHREAD_CREATE_JOINABLE);
   pthread_create (&threads[0], &attr, inc_count, (void *)
&thread_ids[0]);
   pthread_create (&threads[1], &attr, inc_count, (void *)
&thread_ids[1]);
   pthread_create (&threads[2], &attr, watch_count, (void *)
&thread_ids[2]);

   /* Wait for all threads to complete */
   for (i = 0; i < NUM_THREADS; i++)
   {
      pthread_join (threads[i], NULL);
   }
   printf ("Main(): Waited on %d  threads. Done.\n", NUM_THREADS);

   /* Clean up and exit */
   pthread_attr_destroy (&attr);
   pthread_mutex_destroy (&count_mutex);
   pthread_cond_destroy (&count_threshold_cv);
   pthread_exit (NULL);
}
==========================================================================

Here is the gdb log:
==========================================================================
$ gdb ./ptt
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "powerpc-ibm-aix5.1.0.0"...
(gdb) break ptt.c:89
Breakpoint 1 at 0x10000814: file ptt.c, line 89.
(gdb) run
Starting program: /home/gabi/swdev/pthread/ptt
inc_count(): thread 0, count = 1, unlocking mutex
inc_count(): thread 0, count = 2, unlocking mutex
inc_count(): thread 0, count = 3, unlocking mutex
inc_count(): thread 0, count = 4, unlocking mutex
inc_count(): thread 0, count = 5, unlocking mutex
inc_count(): thread 0, count = 6, unlocking mutex
inc_count(): thread 0, count = 7, unlocking mutex
inc_count(): thread 0, count = 8, unlocking mutex
inc_count(): thread 0, count = 9, unlocking mutex
inc_count(): thread 0, count = 10, unlocking mutex
[Switching to Thread 1]

Breakpoint 1, main (argc=1, argv=0x2ff22810) at ptt.c:89
89         pthread_create (&threads[2], &attr, watch_count, (void *)
&thread_ids[2]);
(gdb) info threads
Illegal instruction(coredump)
==========================================================================

The following system libraries versions are installed on the 2 machines:
bos.rte.libpthreads       5.3.0.40
bos.rte.libpthreads       5.2.0.0

Is this a known issue ?
Any special flags that i need to use during the program compilation?

	gabriel

Re: [tbox-l] Need a version of guile-1.6.7 - Part Two

[Reza A. <ar...@au...>]

Hi Ed,

On 27 Aug 2006, 03:18PM CDT, Ed Immenschuh <edj...@ya...> wrote:
> (./guile-snarf-docs -DHAVE_CONFIG_H -I.. -I./..
> -I../libguile-ltdl  -g -O2 -Wall -Wmissing-prototypes
> -fno-strict-aliasing alist.c | \
> ./guile_filter_doc_snarfage --filter-snarfage) >
> alist.doc || { rm alist.doc; false; }
> /bin/sh: 21176 Segmentation fault(coredump)

It looks like either guile-snarf-docs or guile_filter_doc_snarfage is 
crashing.  Please go to the directory containing the core file and run `dbx`.
It should tell you which one.  

Also, once you're at the (dbx) prompt, please use 'where' to get a stack trace.


-- 
Reza Arbab
ar...@au...

[tbox-l] Need a version of guile-1.6.7 - Part Two

[Ed I. <edj...@ya...>]

Hello,

I realized I forgot to show where I am getting the
coredump, in my last email...

Ed

___________________________

nothing to be done for `all-am'.
gmake[3]: Leaving directory
`/mystuff/guile-1.6.8/libguile-ltdl'
gmake[2]: Leaving directory
`/mystuff/guile-1.6.8/libguile-ltdl'
Making all in libguile
gmake[2]: Entering directory
`/mystuff/guile-1.6.8/libguile'
(test -n "" || AWK="nawk"; nawk -f
./guile-func-name-check alist.c)
(./guile-snarf-docs -DHAVE_CONFIG_H -I.. -I./..
-I../libguile-ltdl  -g -O2 -Wall -Wmissing-prototypes
-fno-strict-aliasing alist.c | \
./guile_filter_doc_snarfage --filter-snarfage) >
alist.doc || { rm alist.doc; false; }
/bin/sh: 21176 Segmentation fault(coredump)
gmake[2]: *** [alist.doc] Error 1
gmake[2]: Leaving directory
`/mystuff/guile-1.6.8/libguile'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/mystuff/guile-1.6.8'
gmake: *** [all] Error 2
denali:/mystuff/guile-1.6.8 6 su: 

[tbox-l] Need a version of guile-1.6.7...

[Ed I. <edj...@ya...>]

Hello,
 
 I need to get a version of guile-1.6.7 or
guile-1.8.0, rather than the guile-1.4 that is
currently on the IBM AIX Toolbox webpage.
 
 I have tried to build it myself, but I for some
reason I am getting a coredump when trying to compile
libguile (see below). I am using AIX 5.3, with the gcc
4.0.2 compilers. I've tried it with the gcc 3.4.6
compilers as well, with the same results..

If you can help me, I need both the run-time and
developers parts.

Thanks for any help you can give me...

Ed Immenschuh

[tbox-l] Joel Wheeler/Burlington/IBM is out of the office.

[Joel W. <jwh...@us...>]

I will be out of the office starting  08/23/2006 and will not return until
08/28/2006.

I will be checking email periodically.

Re: [tbox-l] bug with tar --bzip2

[Reza A. <ar...@au...>]

Hi J=F8rn,

On 20 Aug 2006, 04:50PM CDT, J=F8rn Amundsen <Jor...@nt...> wrot=
e:
> frigg:src$ tar --bzip2 -tf tclx8.4.tar.bz2
> tar: Unaligned block (5000 bytes) in archive
> tar: Error is not recoverable: exiting now

This seems to be a known bug in tar 1.14:
<http://savannah.gnu.org/bugs/?func=3Ddetailitem&item_id=3D8902>.

I rebuilt tar-1.14 with a patch to fix this.  Here is the new package:
<ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/tar/tar-=
1.14-2.aix5.1.ppc.rpm>

I will also request that we be allowed to update the Toolbox with the=20
latest version of tar.  It looks like 1.16 is imminent.

Thanks for pointing this out!


--=20
Reza Arbab
ar...@au...

[tbox-l] bug with tar --bzip2

[<Jor...@nt...>]

There seems to be a problem with the -j switch to tar (--bzip2):

frigg:src$ uname -a
AIX frigg 3 5 00021F0CD700 powerpc unknown AIX
frigg:src$ type tar
tar is hashed (/usr/linux/bin/tar)
frigg:src$ rpm -qf /usr/linux/bin/tar
tar-1.14-1
frigg:src$ tar --bzip2 -tf tclx8.4.tar.bz2
tar: Unaligned block (5000 bytes) in archive
tar: Error is not recoverable: exiting now

The above bz2-compressed archive is the original v.8.4 distro of tclx,
and is in perfect condition:

frigg:src$ bzip2 -d -c tclx8.4.tar.bz2 | tar tf - | head -5
tclx8.4/
tclx8.4/doc/
tclx8.4/doc/Keylist.3
tclx8.4/doc/CmdWrite.3
tclx8.4/doc/TclXInit.3


So there seems to be a problem with the 1.14-1 tar binary bzip2
decompression.

Rgds --J=F8rn Amundsen

Re: [tbox-l] GNUstep on AIX?

[Reza A. <ar...@au...>]

Hi Mark,

On 15 Aug 2006, 01:02PM CDT, Mark Bush <Mar...@bu...> wrote:
> Is there any intent to include GNUstep in the toolbox?

I'd be happy to take the steps to include it in the Toolbox.  However, as
far as I know, nobody around here has ported it.

Once it's working, let us know and we can try to package it in an RPM and put 
it on the site for everybody.


-- 
Reza Arbab
ar...@au...

[tbox-l] Justin Anderson/TECHSRV/STIP/UBOC is out of the office.

[<Jus...@ub...>]

I will be out of the office starting  07/27/2006 and will not return until
08/17/2006.

I will respond to your message when I return.


******************************************************************************
This communication (including any attachments) may contain privileged or
confidential information intended for a specific individual and purpose, 
and is protected by law.  If you are not the intended recipient, you should
delete this communication and/or shred the materials and any attachments and
are hereby notified that any disclosure, copying, or distribution of this
communication, or the taking of any action based on it, is strictly prohibited.

Thank you.

[tbox-l] GNUstep on AIX?

[Mark B. <Mar...@bu...>]

Is there any intent to include GNUstep in the toolbox?  Or anyone know of
anyone who has successfully compiled the base system (Foundation framewor=
k)
under AIX 5.x?

Have tried to get it to work myself with little success.  I can persuade =
it to
build by hacking NSProcessInfo.m as none of the methods it has to extract=
 the
argument list seem to be supported under AIX, so to get it to compile I f=
udged
it.  But any application built against the library doesn't seem to be abl=
e to
access any of the classes in it. :(

Thanks,
Mark

[tbox-l] Tom Flynn is out of the office.

[Tom F. <tr...@us...>]

I will be out of the office starting  07/14/2006 and will not return until
08/06/2006.

I will be out of the office  Monday July 17 , returning  Monday, Aug 7th..I
will respond to your message upon returing.

Re: [tbox-l] Problems with Crypto Content Site?

[Timothy B. <tjb...@gm...>]

On 7/14/06, Wil Cooley <wc...@na...> wrote:
>
> On Fri, 2006-07-14 at 09:40 -0500, Reza Arbab wrote:
> > Hi Larry,
> >
> > On 14 Jul 2006, 09:27AM CDT, Larry Starr <la...@fu...> wrote:
> > > Is there a, known, problem with that part of the site?
> >
> > Not sure what's going on, but I've reported this to our webmaster.
>
> Is there a good reason why, over half a decade after the US government
> relaxed restrictions on the export of open source cryptographic software
> source and binaries, IBM insists on locking them behind a lot of tedious
> click-through agreements instead of just distributing it openly with
> everything else?
>
> Wil
> --
> Wil Cooley <wc...@na...>
> Naked Ape Consulting, Ltd



I hope it is obvious I can't answer authoritatively for IBM, but with all
the horror stories I have heard from IBMers (and exIBMers) about their
lawyers and internal security practitioners, it wouldn't surprise me if the
rules were kept in effect for 50 years past the dropping of restrictions,
just to be safe.

I really feel for these folks

Re: [tbox-l] Compiling PERL modules

[Wil C. <wc...@na...>]

On Fri, 2006-07-14 at 16:53 -0400, Scott Fletcher wrote:
> I have one quick question that came to my mind.  In the past when I
> compiled Perl then upon installing it would I have to keep-on answering
> some questions about Perl.  I didn't really like that because I don't
> know the answers to some of the questions. =20
>=20
> So, is it possible to make it all automatic when installing Perl?

That's what '-des' (or '-d -e -s') does:

$ bash Configure -h
Usage: Configure [-dehrsEKOSV] [-f config.sh] [-D symbol] [-D symbol=3Dvalu=
e]
                 [-U symbol] [-U symbol=3D] [-A command:symbol...]
  -d : use defaults for all answers.
  -e : go on without questioning past the production of config.sh.
...
  -s : silent mode, only echoes questions and essential information.

Wil
--=20
Wil Cooley <wc...@na...>
Naked Ape Consulting, Ltd

Re: [tbox-l] Compiling PERL modules

[Scott F. <SFl...@ab...>]

I have one quick question that came to my mind.  In the past when I
compiled Perl then upon installing it would I have to keep-on answering
some questions about Perl.  I didn't really like that because I don't
know the answers to some of the questions. =20

So, is it possible to make it all automatic when installing Perl?

Thanks...

Re: [tbox-l] Problems with Crypto Content Site?

[Wil C. <wc...@na...>]

On Fri, 2006-07-14 at 09:40 -0500, Reza Arbab wrote:
> Hi Larry,
>=20
> On 14 Jul 2006, 09:27AM CDT, Larry Starr <la...@fu...> wrote:
> > Is there a, known, problem with that part of the site?
>=20
> Not sure what's going on, but I've reported this to our webmaster.

Is there a good reason why, over half a decade after the US government
relaxed restrictions on the export of open source cryptographic software
source and binaries, IBM insists on locking them behind a lot of tedious
click-through agreements instead of just distributing it openly with
everything else?

Wil
--=20
Wil Cooley <wc...@na...>
Naked Ape Consulting, Ltd

Re: [tbox-l] Compiling PERL modules

[Wil C. <wc...@na...>]

On Tue, 2006-07-11 at 19:08 -0500, John Tesch wrote:
>=20
> Because the PERL for AIX was compiled with the IBM C compiler, I've
> found you really need to have it installed when compiling other
> modules.  Trying to use gcc just doesn't work.  In looking at other
> mailing lists the requirement to compile modules with the same
> compiler as PERL was compiled with seems to not be just an IBM AIX
> problem, but quite common.=20

I build my own Perl, because it's always a little doubtful whether
libraries (and XS modules) built with a different compiler than Perl
itself is built with will work, even between GCC releases, much less a
wholly different compiler.

Building Perl with GCC is pretty straight-forward, but there are
gotchas--the common GCC message '-b must be at the beginning of the
command' is due to GCC receiving CFLAGS (or LDFLAGS?) intended for xlC
or a direct call to ld.  I noticed with Perl 5.8.7 that there were
problems with the documented way of using GCC, because the Configure
script would use CC=3Dgcc but *FLAGS intended for xlC.  Here's the
incantation I found that worked:

    bash ${PERLSRC}/Configure -des  \
        -Dcc=3Dgcc -Dusethreads       \
        -Dprefix=3D/usr/local/perl5   \
        -Dmksymlinks

Wil
--=20
Wil Cooley <wc...@na...>
Naked Ape Consulting, Ltd

Re: [tbox-l] Compiling PERL modules

[Aaron M. <aar...@gm...>]

On 7/13/06, Mike Austin <mg...@uv...> wrote:
> John Tesch wrote:
>
> This still works for us:
>
> http://marc.10east.com/?l=aixtoolbox-list&m=102372189920066&w=2
>
> Basically, you change the Perl Config.PM to reflect gcc instead of xlc -
> most Perl module builds just work after that.
>
> Good luck,
> mga.

That is a pretty cool piece of info.  The following also works for
most perl modules (at least when I was working with AIX 5.1):

perl Makefile.PL CC=gcc

-- 
Aaron W Morris (decep) <aar...@gm...>

Re: [tbox-l] Problems with Crypto Content Site?

[Reza A. <ar...@au...>]

Hi Larry,

On 14 Jul 2006, 09:27AM CDT, Larry Starr <la...@fu...> wrote:
> Is there a, known, problem with that part of the site?

Not sure what's going on, but I've reported this to our webmaster.


-- 
Reza Arbab
ar...@au...

[tbox-l] Problems with Crypto Content Site?

[Larry S. <la...@fu...>]

For the past couple of days the "Crypto" site has been extreemly slow, to 
completely non-responsive.

Is there a, known, problem with that part of the site?
-- 
Larry G. Starr - la...@fu... or st...@gl...
Software Engineer: Full Compass Systems LTD.
Phone: 608-831-7330 x 1347  FAX: 608-831-6330
===================================================================
There are only three sports: bullfighting, mountaineering and motor
racing, all the rest are merely games! - Ernest Hemmingway

Re: [tbox-l] Compiling PERL modules

[Mike A. <mg...@uv...>]

John Tesch wrote:
> 
> Because the PERL for AIX was compiled with the IBM C compiler, I've 
> found you really need to have it installed when compiling other modules. 
>  Trying to use gcc just doesn't work.  In looking at other mailing lists 
> the requirement to compile modules with the same compiler as PERL was 
> compiled with seems to not be just an IBM AIX problem, but quite common.

This still works for us:

http://marc.10east.com/?l=aixtoolbox-list&m=102372189920066&w=2

Basically, you change the Perl Config.PM to reflect gcc instead of xlc - 
most Perl module builds just work after that.

Good luck,
mga.

Re: [tbox-l] Compiling PERL modules

[Scott F. <SFl...@ab...>]

Oh I See.  Yuck!!  I know the feeling now.  It should be more C/C++
compiler independent.  :-)

=20

________________________________

From: Hurt, Richard [mailto:Ric...@yu...]=20
Sent: Wednesday, July 12, 2006 12:17 PM
To: Scott Fletcher; aix...@li...
Subject: RE: [tbox-l] Compiling PERL modules

=20

Scott,

=20

It's not a problem getting Perl, it's that the version provided by IBM
is compiled with the IBM compiler and modules compiled with any other
compiler will fail.  The solution is to either install the IBM compiler
($$$) and use that to compile your Perl modules, or build Perl and your
modules from GCC (Open Source & free :).

=20

Later...=20
  Richard=20

=20

________________________________

From: aix...@li...
[mailto:aix...@li...] On Behalf Of
Scott Fletcher
Sent: Wednesday, July 12, 2006 8:35 AM
To: aix...@li...
Subject: Re: [tbox-l] Compiling PERL modules

With AIX version 5.x, you can get perl install right from the AIX 5.x
CDs via the "smit install_latest" command.  Well, that would depend on
the Perl's minimum required version you need. =20

=20

________________________________

From: aix...@li...
[mailto:aix...@li...] On Behalf Of
Hurt, Richard
Sent: Wednesday, July 12, 2006 7:53 AM
To: John Tesch; aix...@li...
Subject: Re: [tbox-l] Compiling PERL modules

=20

Yes, Perl is notoriously finicky about it's modules being built with the
same compiler.  I ran into this problem 6 months ago and eventually had
to compile Perl myself using GCC.  It wasn't fun, but at least I have a
Perl that works now.  :/ =20

=20

You might also get a precompiled Perl install from the Bull site
(http://www.bullfreeware.com/) or the PDSL
http://aixpdslib.seas.ucla.edu/).

=20

Later...=20
  Richard=20

________________________________

From: aix...@li...
[mailto:aix...@li...] On Behalf Of John
Tesch
Sent: Tuesday, July 11, 2006 8:08 PM
To: aix...@li...
Subject: [tbox-l] Compiling PERL modules


Because the PERL for AIX was compiled with the IBM C compiler, I've
found you really need to have it installed when compiling other modules.
Trying to use gcc just doesn't work.  In looking at other mailing lists
the requirement to compile modules with the same compiler as PERL was
compiled with seems to not be just an IBM AIX problem, but quite common.


DISCLAIMER:
This communication is confidential and may be legally privileged. If you
are not the intended recipient, (i) please do not read or disclose to
others, (ii) please notify the sender by reply mail, and (iii) please
delete this communication from your system. Failure to follow this
process may be unlawful. Thank you for your cooperation.

DISCLAIMER:
This communication is confidential and may be legally privileged. If you
are not the intended recipient, (i) please do not read or disclose to
others, (ii) please notify the sender by reply mail, and (iii) please
delete this communication from your system. Failure to follow this
process may be unlawful. Thank you for your cooperation.

Re: [tbox-l] Compiling PERL modules

[Hurt, R. <Ric...@yu...>]

Scott,
=20
It's not a problem getting Perl, it's that the version provided by IBM
is compiled with the IBM compiler and modules compiled with any other
compiler will fail.  The solution is to either install the IBM compiler
($$$) and use that to compile your Perl modules, or build Perl and your
modules from GCC (Open Source & free :).
=20
Later...=20
  Richard=20
=20
________________________________

From: aix...@li...
[mailto:aix...@li...] On Behalf Of
Scott Fletcher
Sent: Wednesday, July 12, 2006 8:35 AM
To: aix...@li...
Subject: Re: [tbox-l] Compiling PERL modules



With AIX version 5.x, you can get perl install right from the AIX 5.x
CDs via the "smit install_latest" command.  Well, that would depend on
the Perl's minimum required version you need. =20

=20

________________________________

From: aix...@li...
[mailto:aix...@li...] On Behalf Of
Hurt, Richard
Sent: Wednesday, July 12, 2006 7:53 AM
To: John Tesch; aix...@li...
Subject: Re: [tbox-l] Compiling PERL modules

=20

Yes, Perl is notoriously finicky about it's modules being built with the
same compiler.  I ran into this problem 6 months ago and eventually had
to compile Perl myself using GCC.  It wasn't fun, but at least I have a
Perl that works now.  :/ =20

=20

You might also get a precompiled Perl install from the Bull site
(http://www.bullfreeware.com/) or the PDSL
http://aixpdslib.seas.ucla.edu/).

=20

Later...=20
  Richard=20

________________________________

From: aix...@li...
[mailto:aix...@li...] On Behalf Of John
Tesch
Sent: Tuesday, July 11, 2006 8:08 PM
To: aix...@li...
Subject: [tbox-l] Compiling PERL modules


Because the PERL for AIX was compiled with the IBM C compiler, I've
found you really need to have it installed when compiling other modules.
Trying to use gcc just doesn't work.  In looking at other mailing lists
the requirement to compile modules with the same compiler as PERL was
compiled with seems to not be just an IBM AIX problem, but quite common.


DISCLAIMER:
This communication is confidential and may be legally privileged. If you
are not the intended recipient, (i) please do not read or disclose to
others, (ii) please notify the sender by reply mail, and (iii) please
delete this communication from your system. Failure to follow this
process may be unlawful. Thank you for your cooperation.



This communication is confidential and may be legally privileged.  If =
you are not the intended recipient, (i) please do not read or disclose =
to others, (ii) please notify the sender by reply mail, and (iii) please =
delete this communication from your system.  Failure to follow this =
process may be unlawful.  Thank you for your cooperation.