Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.misc > #14526 > unrolled thread

LD_LIBRARY_PATH is ineffective

Back to article view | Back to comp.os.linux.misc

Contents

  LD_LIBRARY_PATH is ineffective newbie2 <xsli2@yahoo.com> - 2015-04-13 11:08 -0700
    Re: LD_LIBRARY_PATH is ineffective Chick Tower <c.tower@deadspam.com> - 2015-04-14 18:30 +0000
    Re: LD_LIBRARY_PATH is ineffective William Unruh <unruh@invalid.ca> - 2015-04-14 23:20 +0000
    Re: LD_LIBRARY_PATH is ineffective A Guy Called Tyketto <tyketto@sbcglobal.net.invalid> - 2015-04-18 04:32 +0000

#14526 — LD_LIBRARY_PATH is ineffective

We delivered a software to our clients. The software is linked to some dynamice library files, which are provided by us too.

On our machine, we set LD_LIBRARY_PATH pointing to these *.so files location, and the software runs fine.

However, on our client's hand, the software cannot find *.so files, regardless setting LD_LIBRARY_PATH

I googled and it says SELinux for security reason, LD_LIBRARY_PATH is turned off etc. But their linux machines are not SELinux.

Is anyway to solve this problem?

Thank you.

[toc] | [next] | [standalone]

#14540

On 2015-04-13, newbie2 wrote:
> We delivered a software to our clients. The software is linked to some 
> dynamice library files, which are provided by us too.
>
> On our machine, we set LD_LIBRARY_PATH pointing to these *.so files 
> location, and the software runs fine.
>
> However, on our client's hand, the software cannot find *.so files, 
> regardless setting LD_LIBRARY_PATH
>
> I googled and it says SELinux for security reason, LD_LIBRARY_PATH is 
> turned off etc. But their linux machines are not SELinux.
>
> Is anyway to solve this problem?

I'm not a developer, so I might not have a clue.  If you're providing
the executable and the dynamic libraries, would it be possible to put
everything in one directory, say in /opt/yoursoftware?  Maybe that would
solve the problem.
-- 
                                 Chick Tower

For e-mail:  colm DOT sent DOT towerboy AT xoxy DOT net

[toc] | [prev] | [next] | [standalone]

#14554

On 2015-04-13, newbie2 <xsli2@yahoo.com> wrote:

Probably the way the system is set up. Since we have no idea of that, we
cannot help. 
Anyway you could try strace and see what files are actually called in
searching for the .so files.

> We delivered a software to our clients. The software is linked to some dynamice library files, which are provided by us too.
>
> On our machine, we set LD_LIBRARY_PATH pointing to these *.so files location, and the software runs fine.
>
> However, on our client's hand, the software cannot find *.so files, regardless setting LD_LIBRARY_PATH
>
> I googled and it says SELinux for security reason, LD_LIBRARY_PATH is turned off etc. But their linux machines are not SELinux.
>
> Is anyway to solve this problem?
>
> Thank you.

[toc] | [prev] | [next] | [standalone]

#14591

newbie2 <xsli2@yahoo.com> wrote:
> We delivered a software to our clients. The software is linked to some dynamice library files, which are provided by us too.
> 
> On our machine, we set LD_LIBRARY_PATH pointing to these *.so files location, and the software runs fine.
> 
> However, on our client's hand, the software cannot find *.so files, regardless setting LD_LIBRARY_PATH
> 
> I googled and it says SELinux for security reason, LD_LIBRARY_PATH is turned off etc. But their linux machines are not SELinux.
> 
> Is anyway to solve this problem?
> 
> Thank you.

	Are you running SELinux on the machine in question?

	If not, have a look at /etc/ld.so.conf. That should tell you the
directories that ldconfig will look at to find *.so libraries. It should
contain something like:

	/usr/lib
	/usr/local/lib
	/lib

	Or something similar. For something not already using any
default library directories (like something not installed by default by
the OS install), I'd add /usr/local/lib to that file, copy the library
to /usr/local/lib, followed by running 'ldconfig -v'. That should not
only show the directories that ldconfig would look at, but the libraries 
it would run against. In the section for /usr/local/lib, you should see
the library there.

	This is independent of setting LD_LIBRARY_PATH, as that would
exist for the duration of a given session. Setting it this way should
keep it there permanently. ldconfig should be run during the next
reboot, so it should always be there.

	Finally, you could run 'ldd /path/to/executable' to see if any
other libraries are needed.

							BL.
-- 
Brad Littlejohn                         | Email:     tyketto@sbcglobal.net
Unix Systems Administrator,             |           tyketto@ozemail.com.au
Web + NewsMaster, BOFH.. Smeghead! :)   |   http://www.wizard.com/~tyketto
  PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569  F620 C819 199A E319 F0BF

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.misc

csiph-web