<?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 Where is xdr_callmsg() ? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/where-is-xdr-callmsg/m-p/2681669#M723217</link>
    <description>&lt;BR /&gt;When compiling sfs, I get:&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;&lt;BR /&gt;c++ -g -O2 -Wall -o nfsmounter domount.o mpfsnode.o nfsfd.o nfsmounter.o safechdir.o staleserv.o uvfsmount.o  ../sfsmisc/.libs/libsfsmisc.a ../svc/.libs/libsvc.a ../crypt/.libs/libsfscrypt.a ../arpc/.libs/libarpc.a ../async/.libs/libasync.a /pkg/gmp/gmp__v3.1.1.dist/gmp/lib/libgmp.a -lnsl&lt;BR /&gt;/usr/ccs/bin/ld: Unsatisfied symbols:&lt;BR /&gt;   xdr_callmsg(XDR *, rpc_msg *)(first referenced in ../arpc/.libs/libarpc.a(acallrpc.o)) (code)&lt;BR /&gt;collect2: ld returned 1 exit status&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;&lt;BR /&gt;What librariy does xdr_callmsg() reside in?&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 12 Mar 2002 21:32:50 GMT</pubDate>
    <dc:creator>Jack Cummings</dc:creator>
    <dc:date>2002-03-12T21:32:50Z</dc:date>
    <item>
      <title>Where is xdr_callmsg() ?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/where-is-xdr-callmsg/m-p/2681669#M723217</link>
      <description>&lt;BR /&gt;When compiling sfs, I get:&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;&lt;BR /&gt;c++ -g -O2 -Wall -o nfsmounter domount.o mpfsnode.o nfsfd.o nfsmounter.o safechdir.o staleserv.o uvfsmount.o  ../sfsmisc/.libs/libsfsmisc.a ../svc/.libs/libsvc.a ../crypt/.libs/libsfscrypt.a ../arpc/.libs/libarpc.a ../async/.libs/libasync.a /pkg/gmp/gmp__v3.1.1.dist/gmp/lib/libgmp.a -lnsl&lt;BR /&gt;/usr/ccs/bin/ld: Unsatisfied symbols:&lt;BR /&gt;   xdr_callmsg(XDR *, rpc_msg *)(first referenced in ../arpc/.libs/libarpc.a(acallrpc.o)) (code)&lt;BR /&gt;collect2: ld returned 1 exit status&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;&lt;BR /&gt;What librariy does xdr_callmsg() reside in?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 12 Mar 2002 21:32:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/where-is-xdr-callmsg/m-p/2681669#M723217</guid>
      <dc:creator>Jack Cummings</dc:creator>
      <dc:date>2002-03-12T21:32:50Z</dc:date>
    </item>
    <item>
      <title>Re: Where is xdr_callmsg() ?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/where-is-xdr-callmsg/m-p/2681670#M723218</link>
      <description>/usr/lib/libnsl.sl</description>
      <pubDate>Tue, 12 Mar 2002 21:42:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/where-is-xdr-callmsg/m-p/2681670#M723218</guid>
      <dc:creator>S.K. Chan</dc:creator>
      <dc:date>2002-03-12T21:42:26Z</dc:date>
    </item>
    <item>
      <title>Re: Where is xdr_callmsg() ?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/where-is-xdr-callmsg/m-p/2681671#M723219</link>
      <description>&lt;BR /&gt;Well, that's what I thought, too, and that's why it's on the command line. &lt;BR /&gt;&lt;BR /&gt;Any idea why the linker isn't picking it up? &lt;BR /&gt;&lt;BR /&gt;--Jack</description>
      <pubDate>Tue, 12 Mar 2002 21:45:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/where-is-xdr-callmsg/m-p/2681671#M723219</guid>
      <dc:creator>Jack Cummings</dc:creator>
      <dc:date>2002-03-12T21:45:48Z</dc:date>
    </item>
  </channel>
</rss>

