OK - some more evidence - look on google for pointers towards problems with thread
local storage and HP compilers ( TLS ) - these are also a source of pain for me ( in
particular with linking in the oracle client libraries for instance ).
Cheers.
On Mon, Apr 30, 2001 at 11:18:45AM -0700, Clint Olsen wrote:
> Hi Brian:
>
> I built Perl with HP's performance C compiler since I've seen gcc on quite
> a few occasions produce considerably slower binaries for the HPPA. We
> already have enough performance problems with Perl as it is :) Our system
> administrator team built 5.005_03 with this compiler, so I know it's
> possible. And Perl 5.6.1 built for me without a hitch whatsoever. It
> wasn't until Inline that a wrench was thrown into the works. If I could
> see some sort of evidence that this was a compiler problem, I would be more
> inclined to revert to gcc... I just don't understand how to analyze this
> output when things fail since it appears to be failing in places it
> shouldn't...
>
> -Clint
>
> On Apr 30, Brian Ingerson wrote:
> >
> > Hmmm. Our tests also used a perl (5.005_03) built with gcc.
> >
> > $Config::Config{cc} eq 'gcc'
> >
> > Piers: Did you build perl yourself from the source? You're not mixing a
> > perl built with HP's compiler, with Inline using gcc. Right?
> >
> > Clint: If you've got the time, try:
> >
> > - installing gcc
> > - put gcc in your path (this will avoid my Makefile.PL bug :)
> > - build a new perl with gcc
> >
> > I believe the easiest way to build perl is:
> >
> > % sh Configure -Dprefix=/base/install/path -ders
> > % make && make test
> > % make install
