Here is a good example. Executing a program
(that was compiled and statically linked on
a licensed OSF machine) under Linux/axp,
you can get the following message:
ERROR: This application will not run successfully unless it is used
on the processor(s) on which it is licensed. The licensed processor(s)
is the one(s) on which the product requiring the EXT-MATH-LIB PAK
will execute. A EXT-MATH-LIB PAK must be registered in the License
Database and activated in the kernel cache before this application will
run. Refer to the installation guide for the product requiring the
EXT-MATH-LIB PAK for license database PAK registration instructions.
This program uses the Digital Extended Math Library (BLAS, etc.).
Of course the DXML is a special package, but I can't see
how the license for DXML differs from that for other
statically linked DEC libraries. You can get away with
statically linking and running other libraries:
print *, 'hello, sin(5.1)=',sin(5.1)
f77 -o junk junk.f -lcm -non_shared
(move junk to linux/axp system.)
hello, sin(5.1)= -0.9258147
but is it different from trying to use the DXML?
-- from Bob Williams, mailto:email@example.com
-- To unsubscribe: send e-mail to firstname.lastname@example.org with 'unsubscribe' as the subject. Do not send it to email@example.com
Copyright © 1995-1997 Red Hat Software. Legal notices