public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Munipradeep Beerakam <mpradeep@linux.vnet.ibm.com>
To: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] LTP May 2009 build failing on RHEL5.4 pre-Alpha
Date: Thu, 04 Jun 2009 15:56:32 +0530	[thread overview]
Message-ID: <1244111192.17248.0.camel@munipradeep-laptop> (raw)
In-Reply-To: <4A276FFC.9020807@renesas.com>

Hi,

It failed on both x86 and x86_64 architectures

Regards
Muni

On Thu, 2009-06-04 at 15:55 +0900, Nobuhiro Iwamatsu wrote:
> Hi,
> 
> Munipradeep Beerakam wrote:
>  > Hi,
>  >
>  > I tried to build the LTP tarball ltp-full-20090531.tgz on RHEL5.4
>  > pre-Alpha Distribution. But build failed with the following error:
>  >
>  > ------------------------------------------------------------------
>  >
>  > make[4]: Entering directory
>  > `/root/ltp-full-20090531/testcases/kernel/syscalls/sgetmask'
>  > gcc -g -O2 -I../../include -g -Wall -I../../../../include -Wall
>  > sgetmask01.c  -L../../../../lib -lltp -o sgetmask01
>  > sgetmask01.c: In function ‘main’:
>  > sgetmask01.c:142: error: ‘__NR_ssetmask’ undeclared (first use in this
>  > function)
>  > sgetmask01.c:142: error: (Each undeclared identifier is reported only
>  > once
>  > sgetmask01.c:142: error: for each function it appears in.)
>  > make[4]: *** [sgetmask01] Error 1
>  > make[4]: Leaving directory
>  > `/root/ltp-full-20090531/testcases/kernel/syscalls/sgetmask'
>  > make[3]: *** [all] Error 2
>  > make[3]: Leaving directory
>  > `/root/ltp-full-20090531/testcases/kernel/syscalls'
>  > make[2]: *** [all] Error 2
>  > make[2]: Leaving directory `/root/ltp-full-20090531/testcases/kernel'
>  > make[1]: *** [all] Error 2
>  > make[1]: Leaving directory `/root/ltp-full-20090531/testcases'
>  > make: *** [all] Error 2
>  >
>  > ------------------------------------------------------------------
>  >
>  > The variable '__NR_ssetmask' declaration is available in /usr/include
>  >
>  > ~# grep -r "__NR_ssetmask" /usr/include/
>  > /usr/include/bits/syscall.h:#define SYS_ssetmask __NR_ssetmask
>  > /usr/include/asm-i386/unistd.h:#define __NR_ssetmask             69
>  >
>  > What could be the reason for failure?
>  >
> What kind of arch do you use?
> x86_64? I became the same problem too.
> x86_64 does not seem to have this systemcall.
> 
> Best regards,
>   Nobuhiro
> 


------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
looking to deploy the next generation of Solaris that includes the latest 
innovations from Sun and the OpenSource community. Download a copy and 
enjoy capabilities such as Networking, Storage and Virtualization. 
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      reply	other threads:[~2009-06-04 10:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03 11:04 [LTP] LTP May 2009 build failing on RHEL5.4 pre-Alpha Munipradeep Beerakam
2009-06-04  6:55 ` Nobuhiro Iwamatsu
2009-06-04 10:26   ` Munipradeep Beerakam [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=1244111192.17248.0.camel@munipradeep-laptop \
    --to=mpradeep@linux.vnet.ibm.com \
    --cc=iwamatsu.nobuhiro@renesas.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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