Rajat, Yes, you must explicitly link now. Previously LiS installed a getpmsg/putpmsg system call that could be accessed using libc which has a system call interface for getpmsg/putpmsg. Newer versions (after 2.14 something?) overload the read/write system call. Calling getpmsg/putpmsg via libc will now return ENOSYS. Only the libLiS or libpLiS libraries provide a working getpmsg/putpmsg.
This change resulted primarily from RedHat's subborn refusal to export the system call table even though workaround patches were proposed. I suppose that they were suffering from the inability to make good on support promises at the time, because queries and proposals from this group were dealt with quite unprofessionally. But that's all water under the bridge now. Just link your application program -lLiS and you won't have a problem, even on broken RedHat kernels. --brian On Wed, 12 May 2004, [EMAIL PROTECTED] wrote: > > > > > Hi all ... > > While using LiS version 2.16.11, i discovered that getmsg system call > fails with error code 38. This problem was resolved using the earlier > version LiS-2.13.16. > It is to be observed that i was not linking the LiS library to my > executable. > > Is it necessary to link the LiS library explicitly while using the > latest version of LiS ?? > > Looking forward to a qucik response > > thanks n regards .. > Rajat > > _______________________________________________ > Linux-streams mailing list > [EMAIL PROTECTED] > http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams -- Brian F. G. Bidulock � The reasonable man adapts himself to the � [EMAIL PROTECTED] � world; the unreasonable one persists in � http://www.openss7.org/ � trying to adapt the world to himself. � � Therefore all progress depends on the � � unreasonable man. -- George Bernard Shaw � _______________________________________________ Linux-streams mailing list [EMAIL PROTECTED] http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams
