Front page | perl.perl5.porters |
Postings from May 2001
Re: Perl under AIX 4.3.3
From: H . Merijn Brand
May 4, 2001 02:16
Re: Perl under AIX 4.3.3
Message ID: 20010504110437.E008.H.M.BRAND@hccnet.nl
On Wed, 25 Apr 2001 17:59:29 +0200, <Armin.Kunaschik@varetis.de> wrote:
> >I have no experience with this version of the compiler. AFAIK AIX 4.3 best
> >works with VAC.
> ibmcxx was released before vac 4.x and included a C and C++ compiler...
> but because there were problems with the makefile support of VAC++ 4 we
> used to
> stay with 3.6.6.
> >Though I know 188.8.131.52 is available, but we didn't pay for it (yet)
> 5.0.2 is out some days... I have checked with this version (on another
> 4.3.3 host)
> and get the same results.
> >which could imply that you are unable to run lslpp. DRAT!
> >(the fact that you included the output of lslpp proves otherwise: I'm
> lslpp works everytime not depending on the user...
> >I do not have 5.6.1 by hand right now. Can you check if this section is
> also in
> ibmcxx is not listed in the aix hint file. There was a bug in the
> optimization but
> as I remember it's already fixed... there should be no need to turn off
> >HTH. (please try again with -Doptimize=none
> No change. Same compiler errors.
> To show that it's not the compiler I have installed the latest 3.1.4 C
> compiler (184.108.40.206)
> on 4.3.3 and tried with your configure options.
> While installing the compiler precompiled headers are generated for 4.2...
> I think AIX 4.3 is not supported by xlC 3.1.4.
> The output looks familiar:
Would the following have any effects to your problem?
On Thu, 3 May 2001 20:53:38 -0400 (EDT), Andy Dougherty <email@example.com> wrote:
> On Thu, 3 May 2001, David Leigh wrote:
> > Hello,
> > I was experiencing the same problem with perl 5.6.1, aix 4.3.3, and vac
> > 5.0.2. But the problem disappears if you answer 'n' to using
> > /usr/bin/nm in Configure.
> > Not sure where the bug is, but it's decent workaround.
> If you think this is a fairly generic problem, you can set usenm in
> hints/aix.sh. (It's a safe thing to do -- it causes Configure to take
> longer, but at least it's apparently more likely to get the right answer.)
> This is the sort of thing that's extremely difficult for anyone without
> access to an AIX system to do much else about. Why nm isn't helping is
> beyond me. Perhaps one of the lib/syscalls or whatever hooks that AIX
> uses has changed?
> I confess I've been too swamped to follow through on the other info sent
> me, but if Configure -Uusenm fixes things, then let's go with that.
H.Merijn Brand Amsterdam Perl Mongers (http://www.amsterdam.pm.org/)
using perl-5.6.1, 5.7.1 & 623 on HP-UX 10.20 & 11.00, AIX 4.2, AIX 4.3,
WinNT 4, Win2K pro & WinCE 2.11 often with Tk800.022 &/| DBD-Unify