OpenROAD icon indicating copy to clipboard operation
OpenROAD copied to clipboard

libortools.so.9: cannot open shared object file: No such file or directory

Open juliannz opened this issue 1 year ago • 3 comments

Describe the bug

I have the same problem as described in issue #2608, but without docker usage. I installed or-tools manually, as the binarys are not available for all dists. ldd build/src/openroad|grep or gives the correct result, but ldd <install-prefix>/bin/openroad|grep or gives libortools.so.9 => not found. I already tried to change the runtime path and set it to <install-prefix>, but this doesnt change anything...

Workarounds:

  • just install or-tools to /opt
  • rm <install-prefix>/bin/openroad && ln -s build/src/openroad <install-prefix>/bin/openroad

but both are not that satisfying...

Expected Behavior

<install-prefix>/bin/openroad shouldnt fail

Environment

doesnt matter imao

To Reproduce

build using or-tools not installed to /opt

Relevant log output

No response

Screenshots

No response

Additional Context

No response

juliannz avatar Jun 10 '24 08:06 juliannz

Have you tried setting your LD_LIBRARY_PATH to find the .so? What platform are you using that requires manual installation.

maliberty avatar Jun 10 '24 12:06 maliberty

Thanks for the hint, I googled a bit and adding set(CMAKE_INSTALL_RPATH_USE_LINK_PATH TRUE) after my changes to the build file resolves the issue (: or-tools is available again for Ubuntu 20, but wasnt in the last release. So you're right, pretty rare use case that one needs to build it from source^^ Still, if youre interested, I can provide my fix via pr or so (but after I finished my current project)...

juliannz avatar Jun 10 '24 13:06 juliannz

A PR would be appreciated.

maliberty avatar Jun 10 '24 13:06 maliberty

Closing as the problem looks to be resolved. Please reopen if the problem is still happening on the latest version.

vvbandeira avatar Aug 22 '25 14:08 vvbandeira