public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: "Kamboju, Naresh" <naresh.kamboju@ap.sony.com>
Cc: ltp-list <ltp-list@lists.sf.net>, Le-Rouzic <aime.le-rouzic@bull.net>
Subject: Re: [LTP] Issues of TIRPC test suite of network test cases
Date: Mon, 06 Jul 2009 21:20:37 +0530	[thread overview]
Message-ID: <1246895437.4887.47.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <4A4C685F.9040909@bull.net>

Naresh,

On Thu, 2009-07-02 at 09:57 +0200, Le-Rouzic wrote: 
> Hi,
> 
> Sorry, I have just seen your mail.
> Nevertheless I changed job 6 months ago and I am afraid of not being 
> able to look at this issue.

I think we would need to identify and fix this issue ourselves ;-)

Regards--
Subrata

> 
> Best Regards
> 
> 
> Subrata Modak a écrit :
> > On Fri, 2009-06-26 at 17:03 +0530, Subrata Modak wrote: 
> >   
> >> Hi Rohit,
> >>
> >> On Thu, 2009-06-25 at 23:10 -0700, rohit verma wrote: 
> >>     
> >>> Hi All,
> >>>
> >>> I am getting the following errors with run_rpc_tests.sh test suite in
> >>> LTP May-09 release.
> >>>       
> >> The problem with this part of the testsuite was always there from the
> >> beginning. However, lets ask something from the developer directly.
> >>
> >> Le,
> >>
> >> Can you please look into this ?
> >>     
> >
> > Le,
> >
> > Any comments from your side ??
> >
> > Regards--
> > Subrata
> >
> >   
> >> Regards--
> >> Subrata
> >>
> >>     
> >>> /home/moblin/LTP_NS_MAY/ltp-full-20090531/testcases/network/rpc/rpc-tirpc-full-test-suite/tests_pack/cleaner.c.src:29:29:
> >>> error: tirpc/netconfig.h: No such file or directory
> >>> /home/moblin/LTP_NS_MAY/ltp-full-20090531/testcases/network/rpc/rpc-tirpc-full-test-suite/tests_pack/cleaner.c.src:31:27:
> >>> error: tirpc/rpc/rpc.h: No such file or directory
> >>> /home/moblin/LTP_NS_MAY/ltp-full-20090531/testcases/network/rpc/rpc-tirpc-full-test-suite/tests_pack/cleaner.c.src:32:29:
> >>> error: tirpc/rpc/types.h: No such file or directory
> >>> /home/moblin/LTP_NS_MAY/ltp-full-20090531/testcases/network/rpc/rpc-tirpc-full-test-suite/tests_pack/cleaner.c.src:33:27:
> >>> error: tirpc/rpc/xdr.h: No such file or directory
> >>> /home/moblin/LTP_NS_MAY/ltp-full-20090531/testcases/network/rpc/rpc-tirpc-full-test-suite/tests_pack/cleaner.c.src:34:27:
> >>> error: tirpc/rpc/svc.h: No such file or directory
> >>> mkdir: cannot create directory
> >>> `/home/moblin/LTP_NS_MAY/ltp-full-20090531/testcases/network/rpc/rpc-tirpc-full-test-suite/tests_pack':
> >>> File exists
> >>>
> >>> tests_pack/tirpc_svc_2/tirpc_svc_2.c:29:29: error: tirpc/netconfig.h:
> >>> No such file or directory
> >>> tests_pack/tirpc_svc_2/tirpc_svc_2.c:31:27: error: tirpc/rpc/rpc.h: No
> >>> such file or directory
> >>> tests_pack/tirpc_svc_2/tirpc_svc_2.c:32:29: error: tirpc/rpc/types.h:
> >>> No such file or directory
> >>> tests_pack/tirpc_svc_2/tirpc_svc_2.c:33:27: error: tirpc/rpc/xdr.h: No
> >>> such file or directory
> >>> tests_pack/tirpc_svc_2/tirpc_svc_2.c:34:27: error: tirpc/rpc/svc.h: No
> >>> such file or directory
> >>> tests_pack/tirpc_svc_2/tirpc_svc_2.c: In function main
> >>> tests_pack/tirpc_svc_2/tirpc_svc_2.c:55: error: bool_t undeclared
> >>> (first use in this function)
> >>> tests_pack/tirpc_svc_2/tirpc_svc_2.c:55: error: (Each undeclared
> >>> identifier is reported only once
> >>> tests_pack/tirpc_svc_2/tirpc_svc_2.c:55: error: for each function it
> >>> appears in.)
> >>> tests_pack/tirpc_svc_2/tirpc_svc_2.c:55: error: expected ; before rslt
> >>> tests_pack/tirpc_svc_2/tirpc_svc_2.c:65: error: rslt undeclared (first
> >>> use in this function)
> >>> tests_pack/tirpc_svc_2/tirpc_svc_2.c:66: error: xdrproc_t undeclared
> >>> (first use in this function)
> >>> tests_pack/tirpc_svc_2/tirpc_svc_2.c:66: error: expected ) before xdr_int
> >>> make: *** [all] Error 1
> >>> cc: .c.src: No such file or directory.
> >>>
> >>>
> >>> Similar bug has been already reported to LTP. Please confirm if the
> >>> patch for this bug is merged into next LTP release.
> >>>       
> >> I remember merging all patches to this effect. Please point me to the
> >> patch which i ought have missed ;-)
> >>
> >> Regards--
> >> Subrata
> >>
> >>     
> >>> Regards,
> >>> Gnaneswar
> >>>       
> >> ------------------------------------------------------------------------------
> >> _______________________________________________
> >> Ltp-list mailing list
> >> Ltp-list@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/ltp-list
> >>     
> >
> >
> >
> >   
> 


------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      parent reply	other threads:[~2009-07-06 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26  6:10 [LTP] Issues of TIRPC test suite of network test cases rohit verma
2009-06-26 11:33 ` Subrata Modak
2009-06-30  7:41   ` Subrata Modak
     [not found]     ` <4A4C685F.9040909@bull.net>
2009-07-06 15:50       ` Subrata Modak [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1246895437.4887.47.camel@subratamodak.linux.ibm.com \
    --to=subrata@linux.vnet.ibm.com \
    --cc=aime.le-rouzic@bull.net \
    --cc=ltp-list@lists.sf.net \
    --cc=naresh.kamboju@ap.sony.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox