perl-Tk: Problems on HPUX10.20 B180 Workstations

Dear all,

we have a network of 4 HPUX-Machines with HPUX10.20:
2 B180 Workstations
2 B2000 Workstations (1 of these 2 works as "perl-server")

Running perl-Tk (e.g. "widget") works fine on the B2000 Machines but
on the B180 I get the following error-message:

Can't load '/opt/perl5/lib/site_perl/5.6.1/PA-RISC1.1/auto/Tk/Event/Event.sl
'
for module Tk::Event: Exec format error at /opt/perl5/lib/5.6
.1/PA-RISC1.1/DynaLoader.pm line 206.
at /opt/perl5/lib/site_perl/5.6.1/PA-RISC1.1/Tk.pm line 13
Compilation failed in require at
/opt/perl5/lib/site_perl/5.6.1/PA-RISC1.1/Tk.pm line 13.
BEGIN failed--compilation aborted at
/opt/perl5/lib/site_perl/5.6.1/PA-RISC1.1/Tk.pm line 13.
Compilation failed in require at /opt/perl5/bin/widget line 8.
BEGIN failed--compilation aborted at /opt/perl5/bin/widget line 8.

Tk was installed on the B2000 - I did not know that perl is that
sensitive on different machine types - only on different UX-Versions
such as 10.20 vs. 11.11


Does anybody have a clue?

Thanx
Alex

"Alex F." <v2af@yahoo.de> schrieb im Newsbeitrag =
news:1e8fe2ae.0409092216.3f5b5eb3@posting.google.com...
> we have a network of 4 HPUX-Machines with HPUX10.20:
> 2 B180 Workstations
> 2 B2000 Workstations (1 of these 2 works as "perl-server")
>=20
> Running perl-Tk (e.g. "widget") works fine on the B2000 Machines but
> on the B180 I get the following error-message:
>=20
> Can't load =
'/opt/perl5/lib/site_perl/5.6.1/PA-RISC1.1/auto/Tk/Event/Event.sl'
> for module Tk::Event: Exec format error at /opt/perl5/lib/5.6
> .1/PA-RISC1.1/DynaLoader.pm line 206.

> Tk was installed on the B2000 - I did not know that perl is that
> sensitive on different machine types - only on different UX-Versions
> such as 10.20 vs. 11.11

Hello Alex,

this sounds to me like different processor-types on the both machines =
might be responsible for the problem.
(B180 <=3D> B2000 sounds like a large gap)

B2000 in my /usr/sam/lib/mo/sched.models
B2000   2.0     PA8500
[I couldn't find the B180 in both /usr/sam/lib/mo/sched.models and =
/usr/lib/sched.models. Any hint from the group ?]

So the B2000 is a PA2.0. If you compile here, you will get (by default) =
PA2.0 code, which won't run an anything older. (e.g. PA 1.1)
I would _guess_, B180 is a PA1.1.... (It's no1.0 (too new, all =
workstations (as opposed to servers) are at least PA1.1), but too old =
for 2.0)
[For the C-line I find "C130    2.0     PA8000" <=3D> "C120    1.1e    =
PA7300"]

You can use sam to check on the B180:
Performance-Monitors/System-Properties

If you want to use the same binary on both machines, compile with =
+DAportable.
(This will use the instruction set for PA1.1 but the scheduling for 2.0; =
So your B2000 gets punished by suboptimized opcode and the B180 by wrong =
scheduling (causing probably pipeline-stalls and the like). So the =
binary will run on both machines, but on both machines slower as one =
optimized for this machine)

HTH

Martin

Hi Martin,

I checked out that the B180 is a 9000/778 (PA-Risc 1.1)

Where can I set the "+DAportable"-Option?

I only the following standard-statements from "perlmodinstall":

perl Makefile.PL
nake
make test
su
make install

thanx
Alex


"Martin Jost" <Martin.Jost@siemens.com> wrote in message news:<chs4n0$fbe$1@news.mch.sbs.de
>...
> "Alex F." <v2af@yahoo.de> schrieb im Newsbeitrag
> news:1e8fe2ae.0409092216.3f5b5eb3@posting.google.com... 
>  '/opt/perl5/lib/site perl/5.6.1/PA-RISC1.1/auto/Tk/Event/Event.sl' 
> 
>
> Hello Alex,
>
> this sounds to me like different processor-types on the both machines
> might be responsible for the problem.
> (B180 <=> B2000 sounds like a large gap)
>
> B2000 in my /usr/sam/lib/mo/sched.models
> B2000   2.0     PA8500
> [I couldn't find the B180 in both /usr/sam/lib/mo/sched.models and
> /usr/lib/sched.models. Any hint from the group ?]
>
> So the B2000 is a PA2.0. If you compile here, you will get (by default)
> PA2.0 code, which won't run an anything older. (e.g. PA 1.1)
> I would  guess , B180 is a PA1.1.... (It's no1.0 (too new, all
> workstations (as opposed to servers) are at least PA1.1), but too old
> for 2.0)
> [For the C-line I find "C130    2.0     PA8000" <=> "C120    1.1e
> PA7300"]
>
> You can use sam to check on the B180:
> Performance-Monitors/System-Properties
>
> If you want to use the same binary on both machines, compile with
> +DAportable.
> (This will use the instruction set for PA1.1 but the scheduling for 2.0;
> So your B2000 gets punished by suboptimized opcode and the B180 by wrong
> scheduling (causing probably pipeline-stalls and the like). So the
> binary will run on both machines, but on both machines slower as one
> optimized for this machine)
>
> HTH
>
> Martin

"Alex F." <v2af@yahoo.de> wrote in message
news:1e8fe2ae.0409130648.1816df8a@posting.google.com...
> Hi Martin,
>
> I checked out that the B180 is a 9000/778 (PA-Risc 1.1)
>
> Where can I set the "+DAportable"-Option?

One easy way is to manually edit the CCFLAGS variable in your Makefile to
add +DAportable there.

>
> I only the following standard-statements from "perlmodinstall":
>
> perl Makefile.PL
> nake
> make test
> su
> make install
>
> thanx
> Alex