I'm certainly no expert on this, but I'll throw out a thought.
(Feel free to throw it out yourself, too. ;)

Can all modules be statically linked?  This should enable
A's call to resolve to A, C's call to resolve to C, and
B'c call (by telling it which to use) to resolve to C.

Other than that, I'm afraid I don't know/remember much.

--Glenn


-----Original Message-----
From: Keven Miller [mailto:[log in to unmask]]
Sent: Friday, July 11, 2003 8:31 AM
To: [log in to unmask]
Subject: [HP9000-L] HPUX Loader linking


On MPE, I have program (A) that runs with XL.group.act (B),
XL.PUB.act (C).

(A) contains a procedure Z.
(B) has a reference to procedure Z.
(C) contains a procedure Z, similar parameters but different code.

On MPE, all (A) references to Z are resolved within itself.
All other references to Z from (B) or (C) are resolved in (C).


However on HPUX, all my references to Z are being resolved from (A).
Such that (B) calls Z from program (A), instead of linking to (C).


Anyone aware of this, and ideas of options to get MPE style of linking?
(Besides changing procedure names and all that code editing)

[Small, simple C example files available apon request]

___________________________________________________________________
Keven Miller   mailto:[log in to unmask]   http://www.exegesys.com