"Kent Johnson" <[EMAIL PROTECTED]> writes:

> no problem, i assume you are very busy as well.  

usually ;-)

> i just installed a version of perl 5.005_03 which i tried using
> instead of my 5.004_04 version.  the perl -V on the 5.005 showed
> "cc='gcc'" while the perl -V on the 5.004 showed
> "cc='/opt/ansic/bin/cc'", so perhaps the 5.005 version should work?

It ought to be simpler, since the CC flags will all be correct.

> this is the output i get when i do a (5.005) perl Makefile.PL:

> /opt/gcc/lib/gcc-lib/hppa2.0n-hp-hpux11.00/3.0.1/include/stdlib.h:18,

Ewwww... gcc-3.0??? You *are* a brave man...

My advice is to stay away from gcc-3.0. It is brand-spanking-new(TM),
and it breaks binary compatibility with previous versions. 

> Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration:
>   Platform:
>     osname=hpux, osvers=11.00, archname=PA-RISC1.1
>     uname='hp-ux disco b.11.00 u 9000800 125901587 unlimited-user license
> '
>     hint=recommended, useposix=true, d_sigaction=define
>     usethreads=undef useperlio=undef d_sfio=undef
>   Compiler:
>     cc='gcc', optimize='-O', gccversion=2.9-hppa-991112

Your perl was compiled with gcc 2.9 something... 

That mess that you got could be due to something simple like 'bool'
getting redefined, so you may want to add in -DHAS_BOOL to the compile
line and see if that changes anything. 

But if not, then I'm afraid the only advice I have is to back of to an
earlier version of gcc... I'm using 2.95.4, which has been quite
stable. 

I'm really sorry this is such a mess. The only other thing I have to
offer is it would help if I had an account on an HPUX machine
someplace. The apache foundation has one, but its an old HP10 machine,
and it's missing tons of software I need to compile Xerces. Seeing as
you work for HP, maybe they have a machine outside your firewall I
could get access to.

Cheers,
jas.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to