[omniORB] FW: Incorrect install name for dylib on macOS

Benjamin Bertrand benjamin.bertrand at maxiv.lu.se
Fri May 16 06:42:51 UTC 2025


Hello Duncan,

I sent a question on the mailing list last month.
I know there have been many days off beginning of May ��

This is part of Tango Controls support.
Could you please have a look?

Thanks

Benjamin

From: Benjamin Bertrand <benjamin.bertrand at maxiv.lu.se>
Date: Friday, 18 April 2025 at 11:32
To: omniorb-list at omniorb-support.com <omniorb-list at omniorb-support.com>
Subject: Incorrect install name for dylib on macOS
Hello,

After compiling omniORB 4.3.3, I noticed that we still have issue on macOS.
cpptango is still compiled against the exact version: @rpath/libomniORB4.3.3.dylib (instead of @rpath/libomniORB4.3.dylib).

I thought setting the compatibility version would fix that, but the problem comes from the install name.

$ otool -L libomniORB4.dylib
libomniORB4.dylib:
@rpath/libomniORB4.3.3.dylib (compatibility version 4.3.0, current version 4.3.3) @rpath/libomnithread.4.3.dylib (compatibility version 4.3.0, current version 4.3.0) @rpath/libc++.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1351.0.0)

$ otool -D  libomniORB4.dylib
libomniORB4.dylib:
@rpath/libomniORB4.3.3.dylib

otool -D should return ”@rpath/libomniORB4.3.dylib”

I tested changing the id name with “install_name_tool” and cpptango links against the proper file afterwards.

To fix omniORB, it seems “-install_name” should be passed in LDFLAGS on macOS.
Could that be added to the build system?

Thanks

Benjamin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.omniorb-support.com/pipermail/omniorb-list/attachments/20250516/5b2cdf7f/attachment.htm>


More information about the omniORB-list mailing list