[Info-vax] Linking problem with multiply defined symbols, how to resolve?

[Arne Vajhøj]

On 9/28/2022 3:33 AM, Richard Levitte wrote:
> I have this problem, that I want to build an app or a shareable
> image, which is linked with another shared library, but which also
> implements its own variant of symbols that are defined in that other
> shared library.
> 
> This is intentional.  It works absolutely fine to do this on the
> Unixen I've access to, as well as on Windows...  but VMS fails me.
> 
> Is this at all possible, or must I seek another method to get what I
> want? (there is the possibilty to link with a .OLB library instead of
> a shareable image, but I'd like to explore the possibilities a little
> more before I resort to that)
> 
> An example below.  legacy-dso-legacyprov.OBJ defines all the ERR
> symbols that LINK complains about, and they are also defined by
> OSSL$libcrypto03_shr.EXE.

Is this for VMS support of the OpenSSL 3 provider model?

Arne