<?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 DLKM developmet question in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dlkm-developmet-question/m-p/3739791#M786341</link>
    <description>Hi , All . &lt;BR /&gt;&lt;BR /&gt;I am developing a DLKM for an Itanium box&lt;BR /&gt;running HP-UX 11.23. &lt;BR /&gt;&lt;BR /&gt;If I login as root and build the module - I have a working binary that can be loaded/unloaded by kcmodule as expected.&lt;BR /&gt;&lt;BR /&gt;But if I login as another user and build the module, I have a binary that could not be loaded by kcmodule, giving errors:   &lt;BR /&gt;&lt;BR /&gt;WARNING: MOD: mod_obj_relone: Overrun of module DLT or long branch stub table for module /stand/current/mod/mymodule.&lt;BR /&gt;NOTICE: MOD: mod_obj_load: Relocation in module /stand/current/mod/mymodule failed.&lt;BR /&gt;&lt;BR /&gt;WARNING: mod_deletestr: could not find string in the dump string table&lt;BR /&gt;&lt;BR /&gt;MOD: mod_load_helper: error loading mymodule&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The object files (including modmeta) are binary equal for both builds.&lt;BR /&gt;&lt;BR /&gt;But the results of modlink have 1 byte difference (well, if not look at timestamps).&lt;BR /&gt;Fixing the byte in "nonworking" binary gives us a "working" one.&lt;BR /&gt;&lt;BR /&gt;So,  quiestion - is there any enviroment dependency or whatever that makes modlink produce different binaries ? &lt;BR /&gt;How can I get the "correct" DLKM binary , not being logged in as root ?&lt;BR /&gt;&lt;BR /&gt;Thanks for any suggestions.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Sun, 26 Feb 2006 20:44:15 GMT</pubDate>
    <dc:creator>Alex Shinkin</dc:creator>
    <dc:date>2006-02-26T20:44:15Z</dc:date>
    <item>
      <title>DLKM developmet question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dlkm-developmet-question/m-p/3739791#M786341</link>
      <description>Hi , All . &lt;BR /&gt;&lt;BR /&gt;I am developing a DLKM for an Itanium box&lt;BR /&gt;running HP-UX 11.23. &lt;BR /&gt;&lt;BR /&gt;If I login as root and build the module - I have a working binary that can be loaded/unloaded by kcmodule as expected.&lt;BR /&gt;&lt;BR /&gt;But if I login as another user and build the module, I have a binary that could not be loaded by kcmodule, giving errors:   &lt;BR /&gt;&lt;BR /&gt;WARNING: MOD: mod_obj_relone: Overrun of module DLT or long branch stub table for module /stand/current/mod/mymodule.&lt;BR /&gt;NOTICE: MOD: mod_obj_load: Relocation in module /stand/current/mod/mymodule failed.&lt;BR /&gt;&lt;BR /&gt;WARNING: mod_deletestr: could not find string in the dump string table&lt;BR /&gt;&lt;BR /&gt;MOD: mod_load_helper: error loading mymodule&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The object files (including modmeta) are binary equal for both builds.&lt;BR /&gt;&lt;BR /&gt;But the results of modlink have 1 byte difference (well, if not look at timestamps).&lt;BR /&gt;Fixing the byte in "nonworking" binary gives us a "working" one.&lt;BR /&gt;&lt;BR /&gt;So,  quiestion - is there any enviroment dependency or whatever that makes modlink produce different binaries ? &lt;BR /&gt;How can I get the "correct" DLKM binary , not being logged in as root ?&lt;BR /&gt;&lt;BR /&gt;Thanks for any suggestions.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 26 Feb 2006 20:44:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dlkm-developmet-question/m-p/3739791#M786341</guid>
      <dc:creator>Alex Shinkin</dc:creator>
      <dc:date>2006-02-26T20:44:15Z</dc:date>
    </item>
    <item>
      <title>Re: DLKM developmet question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dlkm-developmet-question/m-p/3739792#M786342</link>
      <description>Wow, I have solved it .&lt;BR /&gt;looks like modlink uses current $PATH , executing ld and maybe some other executables... so the PATH was a bit incorrect in the user's account and another (probably older) versions of ld were in use.&lt;BR /&gt;Anyway, modlink could be more verbous ...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 27 Feb 2006 01:17:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dlkm-developmet-question/m-p/3739792#M786342</guid>
      <dc:creator>Alex Shinkin</dc:creator>
      <dc:date>2006-02-27T01:17:42Z</dc:date>
    </item>
    <item>
      <title>Re: DLKM developmet question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dlkm-developmet-question/m-p/3739793#M786343</link>
      <description>maybe this will be interesting for anyone ...&lt;BR /&gt;&lt;BR /&gt;To be more precise it was GNU nm 2.15 that causes building of unloadable module.&lt;BR /&gt;&lt;BR /&gt;Using HP nm (nm HP Itanium(R) B.12.23 REL 040623) has solved the problem .&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Mar 2006 00:53:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dlkm-developmet-question/m-p/3739793#M786343</guid>
      <dc:creator>Alex Shinkin</dc:creator>
      <dc:date>2006-03-02T00:53:59Z</dc:date>
    </item>
  </channel>
</rss>

