using local shared objects for a stand-alone executable binary

shoelesshunter · 2021-02-01 03:35:49

I was given a tarball and told to 'just run it'

When I unpacked it, it contained a directory we'll cal 'folder' and two .so files 'object1.so' object2.so'

The executable has no extension but is definitely an executable binary we'll call 'binary'

First thing I did was ./binary and of course it complained about missing shared objects. Oddly, it did not ask for either of the two in 'folder' but either way I know I'm in the right direction in thinking I need 'binary' to see objec1.so and object2.so and do it all in the environment of 'folder.'

Am I correct, and if so how do I do this?

Scimmia · 2021-02-01 03:43:53

You start by not hiding all of the relevant information.

Trilby · 2021-02-01 03:52:51

I know exactly what's going on. Let me type out the steps to fix it.

1. Open your terminal and cd to a system directory we'll call 'directory'
2. Once there, run a very specific command that we'll just call 'command'
3. Observe the output of 'command' which we'll call 'result'
4. Once you have 'result' it should be abundantly clear how you can run 'binary'

You're welcome.

shoelesshunter · 2021-02-01 04:07:13

Thanks, I'll be more specific when I get access to the software again. Was writing this from work, from memory.
It is no longer on this system. I plan to have it back though. Thanks.

Arch Linux

#1 2021-02-01 03:35:49

using local shared objects for a stand-alone executable binary

#2 2021-02-01 03:43:53

Re: using local shared objects for a stand-alone executable binary

#3 2021-02-01 03:52:51

Re: using local shared objects for a stand-alone executable binary

#4 2021-02-01 04:07:13

Re: using local shared objects for a stand-alone executable binary

Board footer