Why do FNE archives use 'versioned' shared object files on Linux?

Title

Summary

Why do FNE archives use 'versioned' shared object files on Linux?

Question

We're running our setup on a x64 bit SuSE 11.3 system using the flexnet_client-xt-c-x64_linux-2017.08.0.tgz toolkit. When we link the libFlxClientXT_pic.a and libFlxCommonXT_pic.a archives with our build, the resulting executable requires that we include the versioned files libFlxComm64.so.2017.08 and libFlxCore64.so.2017.08. Is there a reason these 'versioned' shared object files are required rather than just using libFlxCo*64.so files?

Answer

FlexNet Embedded aligned with standard Linux procedures as of the 2016 R2 release.

Here's some more info on how they are used:
https://unix.stackexchange.com/questions/475/how-do-so-shared-object-numbers-work

Was this helpful?

Support Hub

Product

FlexNet Embedded

Visibility

Guest

URL Name

why-do-fne-archives-use-versioned-shared-object-files-on-linux

Are you sure you want to cancel the case creation?

Case closed successfully

Action performed successfully

Upload Attachment

Maximum file size allowed is 3 MB.

File type not supported.

Supported file types:

Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files (.csv) Speadsheets (.xlsx, .xls)

Are you sure you want to close this case

Get Hotline support

Products	Region	Phone Numbers
FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield	North America *	+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America)
	Europe *	+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe)
	Japan *	+81 3-4540-5335 (select option 2)
	Australia *	+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia)
Usage Intelligence (formerly Revulytics) Compliance Intelligence	Please use the Case Portal to submit your support ticket or reach out to your Revenera contact.

Summary

Question

Answer

Related Articles

Please wait...

Case id: 00001065