<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Shared Libraries question in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/shared-libraries-question/m-p/3043053#M809694</link>
    <description>If you want to use a shared library that is not always present, one option is to provide a stub&lt;BR /&gt;version of that library.  Link your executable with ld's +b option so it has a shared library search path that looks first in the system directory and then in your own stub library's directory.  If the system library is not there, then the stub library of the same name will be loaded instead.</description>
    <pubDate>Wed, 06 Aug 2003 19:19:28 GMT</pubDate>
    <dc:creator>Mike Stroyan</dc:creator>
    <dc:date>2003-08-06T19:19:28Z</dc:date>
    <item>
      <title>Shared Libraries question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/shared-libraries-question/m-p/3043052#M809693</link>
      <description>I work in the CIFS Server Group. CIFS Server is based on open source product Samba. What we do is we take this code do some enhancements/changes/customize it to HP-UX &amp;amp; ship it.&lt;BR /&gt;      The problem I'm having is I compile our product with LDAP libraries. When I do a chatr on my daemon I can see that the daemon is expecting this library at run time. So if the library is not there the daemon won't even start. I want to customize this such that irrespective of the libraries present the daemon should start.&lt;BR /&gt;One solution is to use shl_load,dl_open &amp;amp; dl_sym to get the address &amp;amp; call the library functions ourselves.&lt;BR /&gt;What I'm looking for is for hp-ux to be doing all this instead of us  controlling how the library functions are called. May be like a compile time/run time  option.&lt;BR /&gt;</description>
      <pubDate>Wed, 06 Aug 2003 16:48:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/shared-libraries-question/m-p/3043052#M809693</guid>
      <dc:creator>Aruna Prabakar</dc:creator>
      <dc:date>2003-08-06T16:48:39Z</dc:date>
    </item>
    <item>
      <title>Re: Shared Libraries question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/shared-libraries-question/m-p/3043053#M809694</link>
      <description>If you want to use a shared library that is not always present, one option is to provide a stub&lt;BR /&gt;version of that library.  Link your executable with ld's +b option so it has a shared library search path that looks first in the system directory and then in your own stub library's directory.  If the system library is not there, then the stub library of the same name will be loaded instead.</description>
      <pubDate>Wed, 06 Aug 2003 19:19:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/shared-libraries-question/m-p/3043053#M809694</guid>
      <dc:creator>Mike Stroyan</dc:creator>
      <dc:date>2003-08-06T19:19:28Z</dc:date>
    </item>
    <item>
      <title>Re: Shared Libraries question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/shared-libraries-question/m-p/3043054#M809695</link>
      <description>with the latest linker / loader patches PHSS_28869 (11.00) / PHSS_28871 (11.11) you can use the linker option "+lazyload" to build the binary so that it wont complain until the application encounters at run-time a reference to a symbol that has to be resolved by the non-existent library.&lt;BR /&gt;&lt;BR /&gt;i'm sorry for the late response but the patch was not released till now :)</description>
      <pubDate>Tue, 23 Sep 2003 01:28:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/shared-libraries-question/m-p/3043054#M809695</guid>
      <dc:creator>ranganath ramachandra</dc:creator>
      <dc:date>2003-09-23T01:28:44Z</dc:date>
    </item>
  </channel>
</rss>

