As reported in #3035, srt/haicrypt/hcrypt_xpt_srt.c has two definitions of the static variable _hcMsg_SRT_MsgInfo:

// Line: 68
static hcrypt_MsgInfo _hcMsg_SRT_MsgInfo;
// Line: 156
static hcrypt_MsgInfo _hcMsg_SRT_MsgInfo;

One more problem is the .parseMsg field off the structure that is initialized with a pointer to hcryptMsg_SRT_ParseMsg function. The hcryptMsg_SRT_ParseMsg function in its turn uses the static _hcMsg_SRT_MsgInfo internally.

To resolve this interdependency the hcryptMsg_SRT_ParseMsg function is made visible and now requires a pointer to a hcrypt_MsgInfo structure instead of using the static variable implicitly.
The _hcMsg_SRT_MsgInfo can now be const and initialized once the following way:

static const hcrypt_MsgInfo _hcMsg_SRT_MsgInfo = {
	.hdr_len     = HCRYPT_MSG_SRT_HDR_SZ,
	.pfx_len     = HCRYPT_MSG_SRT_PFX_SZ,
	.getKeyFlags = hcryptMsg_SRT_GetKeyFlags,
	.getPki      = hcryptMsg_SRT_GetPki,
	.setPki      = hcryptMsg_SRT_SetPki,
	.resetCache  = hcryptMsg_SRT_ResetCache,
	.indexMsg    = hcryptMsg_SRT_IndexMsg,
};

Fixes #3035.