<?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: C &amp;amp; dynamic libraries.... in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/c-amp-dynamic-libraries/m-p/4646521#M676885</link>
    <description>Defining the library path at compilation time for each binary is the only "best practices" approach we have?, isn't there any system wide solution not involving shell variables?..</description>
    <pubDate>Mon, 14 Jun 2010 14:38:19 GMT</pubDate>
    <dc:creator>Ciro  Iriarte</dc:creator>
    <dc:date>2010-06-14T14:38:19Z</dc:date>
    <item>
      <title>C &amp; dynamic libraries....</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/c-amp-dynamic-libraries/m-p/4646519#M676883</link>
      <description>Hi, what would be the correct way to setup additional directories to look for shared libraries?.&lt;BR /&gt;&lt;BR /&gt;The idea is not to use LD_LIBRARY_PATH but the equivalent in HPUX to "ldconfig" in Linux or "crle" in Solaris.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Jun 2010 15:36:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/c-amp-dynamic-libraries/m-p/4646519#M676883</guid>
      <dc:creator>Ciro  Iriarte</dc:creator>
      <dc:date>2010-06-11T15:36:59Z</dc:date>
    </item>
    <item>
      <title>Re: C &amp; dynamic libraries....</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/c-amp-dynamic-libraries/m-p/4646520#M676884</link>
      <description>(The correct HP-UX terminology is shared libraries.)&lt;BR /&gt;&lt;BR /&gt;You can either link with -L path and these will be included in the runtime lookup paths (rpath).  Or you can link with +b path_list.</description>
      <pubDate>Sat, 12 Jun 2010 11:59:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/c-amp-dynamic-libraries/m-p/4646520#M676884</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2010-06-12T11:59:48Z</dc:date>
    </item>
    <item>
      <title>Re: C &amp; dynamic libraries....</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/c-amp-dynamic-libraries/m-p/4646521#M676885</link>
      <description>Defining the library path at compilation time for each binary is the only "best practices" approach we have?, isn't there any system wide solution not involving shell variables?..</description>
      <pubDate>Mon, 14 Jun 2010 14:38:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/c-amp-dynamic-libraries/m-p/4646521#M676885</guid>
      <dc:creator>Ciro  Iriarte</dc:creator>
      <dc:date>2010-06-14T14:38:19Z</dc:date>
    </item>
    <item>
      <title>Re: C &amp; dynamic libraries....</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/c-amp-dynamic-libraries/m-p/4646522#M676886</link>
      <description>&amp;gt;Defining the library path at link time for each binary is the only "best practices" approach we have?  Isn't there any system wide solution not involving shell variables?&lt;BR /&gt;&lt;BR /&gt;Those are the two solutions.&lt;BR /&gt;You of course can put your shlibs in /usr/lib/, or use $ORIGIN.</description>
      <pubDate>Mon, 14 Jun 2010 18:08:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/c-amp-dynamic-libraries/m-p/4646522#M676886</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2010-06-14T18:08:35Z</dc:date>
    </item>
  </channel>
</rss>

