<?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: ldd reports absolute path dependencies in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ldd-reports-absolute-path-dependencies/m-p/3514005#M701052</link>
    <description>from "man ld"&lt;BR /&gt;&lt;BR /&gt;+cdp oldpath:newpath&lt;BR /&gt;Replace the recorded path for a shared library in the a.out.  In 32-bit mode, ld records the absolute path names of any shared libraries searched at link time in the a.out file.  When the program begins execution, the dynamic loader attaches any shared libraries that were searched at link time. Although you can use the +b and/or +s linker options to direct the dynamic loader to directories to search for the shared libraries, the dynamic loader, as a last resort, searches for the shared libraries in its absolute, recorded path in the a.out.  You can specify more than one shared library oldpath:newpath, but each must be preceded by the +cdp option.&lt;BR /&gt;&lt;BR /&gt;Are you running 32bit or 64bit?&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry d brown jr</description>
    <pubDate>Wed, 30 Mar 2005 08:03:26 GMT</pubDate>
    <dc:creator>harry d brown jr</dc:creator>
    <dc:date>2005-03-30T08:03:26Z</dc:date>
    <item>
      <title>ldd reports absolute path dependencies</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ldd-reports-absolute-path-dependencies/m-p/3514004#M701051</link>
      <description>Hi,&lt;BR /&gt; after compiling a program which uses ORACLE shared libraries, executing "ldd &lt;PROGRAM&gt;" returns all the dependencies as absolute paths, e.g., &lt;BR /&gt;&lt;BR /&gt;/usr/lib/libc.2 =&amp;gt;      /usr/lib/libc.2&lt;BR /&gt;&lt;BR /&gt;instead of&lt;BR /&gt;&lt;BR /&gt;libc.2 =&amp;gt;      /usr/lib/libc.2&lt;BR /&gt;&lt;BR /&gt;. For /usr/lib libraries this is ok, but with oracle libraries, they reside on a directory which is different from target host, so I get a&lt;BR /&gt;&lt;BR /&gt;/usr/lib/dld.sl: Can't open shared library: &lt;ABSOLUTE_PATH_TO_ORACLE&gt;/lib/libclntsh.sl.8.0&lt;BR /&gt;&lt;BR /&gt;, instead of searching the library among LD_LIBRARY_PATH or SHLIB_PATH directories.&lt;BR /&gt;&lt;BR /&gt;How can I tell the linker to insert non-absolute references to external libraries?&lt;BR /&gt;I've tried the +s option, without success.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;&lt;/ABSOLUTE_PATH_TO_ORACLE&gt;&lt;/PROGRAM&gt;</description>
      <pubDate>Wed, 30 Mar 2005 04:10:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ldd-reports-absolute-path-dependencies/m-p/3514004#M701051</guid>
      <dc:creator>Roberto Martinez_6</dc:creator>
      <dc:date>2005-03-30T04:10:32Z</dc:date>
    </item>
    <item>
      <title>Re: ldd reports absolute path dependencies</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ldd-reports-absolute-path-dependencies/m-p/3514005#M701052</link>
      <description>from "man ld"&lt;BR /&gt;&lt;BR /&gt;+cdp oldpath:newpath&lt;BR /&gt;Replace the recorded path for a shared library in the a.out.  In 32-bit mode, ld records the absolute path names of any shared libraries searched at link time in the a.out file.  When the program begins execution, the dynamic loader attaches any shared libraries that were searched at link time. Although you can use the +b and/or +s linker options to direct the dynamic loader to directories to search for the shared libraries, the dynamic loader, as a last resort, searches for the shared libraries in its absolute, recorded path in the a.out.  You can specify more than one shared library oldpath:newpath, but each must be preceded by the +cdp option.&lt;BR /&gt;&lt;BR /&gt;Are you running 32bit or 64bit?&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry d brown jr</description>
      <pubDate>Wed, 30 Mar 2005 08:03:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ldd-reports-absolute-path-dependencies/m-p/3514005#M701052</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2005-03-30T08:03:26Z</dc:date>
    </item>
    <item>
      <title>Re: ldd reports absolute path dependencies</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ldd-reports-absolute-path-dependencies/m-p/3514006#M701053</link>
      <description>compiling in 32 bits, OE in 64 bit. I'll check and answer.</description>
      <pubDate>Wed, 30 Mar 2005 08:24:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ldd-reports-absolute-path-dependencies/m-p/3514006#M701053</guid>
      <dc:creator>Roberto Martinez_6</dc:creator>
      <dc:date>2005-03-30T08:24:26Z</dc:date>
    </item>
    <item>
      <title>Re: ldd reports absolute path dependencies</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ldd-reports-absolute-path-dependencies/m-p/3514007#M701054</link>
      <description>chatr +s enable exe_name&lt;BR /&gt;&lt;BR /&gt;Will tell the dld to use SHLIB_PATH if it can't find the libraries at the absolute addresses quoted by ldd.</description>
      <pubDate>Wed, 30 Mar 2005 09:45:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ldd-reports-absolute-path-dependencies/m-p/3514007#M701054</guid>
      <dc:creator>Stephen Keane</dc:creator>
      <dc:date>2005-03-30T09:45:08Z</dc:date>
    </item>
    <item>
      <title>Re: ldd reports absolute path dependencies</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ldd-reports-absolute-path-dependencies/m-p/3514008#M701055</link>
      <description>you can use the (new! for pa32) linker option "+nodefaultrpath". this will make the linker record only the basenames of libraries specified with -l on the link line. note that&lt;BR /&gt;- you have to make sure that either embedded path or SHLIB_PATH will be able to find these libararies at run-time&lt;BR /&gt;- if you specify full library paths in the link line, they will still be recorded completely.</description>
      <pubDate>Wed, 30 Mar 2005 22:40:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ldd-reports-absolute-path-dependencies/m-p/3514008#M701055</guid>
      <dc:creator>ranganath ramachandra</dc:creator>
      <dc:date>2005-03-30T22:40:25Z</dc:date>
    </item>
    <item>
      <title>Re: ldd reports absolute path dependencies</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ldd-reports-absolute-path-dependencies/m-p/3514009#M701056</link>
      <description>Thank you all, it worked.</description>
      <pubDate>Thu, 31 Mar 2005 05:21:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ldd-reports-absolute-path-dependencies/m-p/3514009#M701056</guid>
      <dc:creator>Roberto Martinez_6</dc:creator>
      <dc:date>2005-03-31T05:21:07Z</dc:date>
    </item>
  </channel>
</rss>

