public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: "Mitani" <mitani@ryobi.co.jp>
To: 'Garrett Cooper' <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Build failure with ltp-2009-12-08 cvs
Date: Wed, 9 Dec 2009 16:43:46 +0900	[thread overview]
Message-ID: <000401ca78a3$56963f50$03c2bdf0$@co.jp> (raw)
In-Reply-To: <364299f40912082106x43632a8ble8bc334070510932@mail.gmail.com>

RHEL4.8's kernel version is 2.6.9-89.ELsmp.
Fedora 3 has kernel 2.6.9-1.667.

But Fedora3 and RHEL4.8 diverged halfway, and now they seem to be
different each other.

If you want some other informations, I offer them.



I heard that CentOS4.8 had kernel of the version same as RHEL4.8.

Thank you--

-Tomonori Mitani

-----Original Message-----
From: Garrett Cooper [mailto:yanegomi@gmail.com] 
Sent: Wednesday, December 09, 2009 2:07 PM
To: Mitani
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Build failure with ltp-2009-12-08 cvs

On Tue, Dec 8, 2009 at 2:16 AM, Mitani <mitani@ryobi.co.jp> wrote:
> Hi,
>
>
> I tried to "make" with "ltp-2009-12-08.tar.gz" version
> in RHEL4.8 (kernel 2.6.9-89.ELsmp) and x86 architecture.
>
> But it failed by following message:
>
> ------------
> make[4]: Entering directory
> `/home/LTP/ltp-2009-12-08/testcases/kernel/syscalls/get_mempolicy'
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall
> -I/home/LTP/ltp-2009-12-08/testcases/kernel/include
>
-I/home/LTP/ltp-2009-12-08/testcases/kernel/syscalls/get_mempolicy/../utils
> -I../../../../include -I../../../../include   -L../../../../lib
> get_mempolicy01.c   -lltp -lnuma -o get_mempolicy01
> In file included from get_mempolicy01.c:58:
>
/home/LTP/ltp-2009-12-08/testcases/kernel/syscalls/get_mempolicy/../utils/nu
> maif.h:88: error: redefinition of 'nodemask_set'
> /usr/include/numa.h:45: error: previous definition of 'nodemask_set' was
> here
> make[4]: *** [get_mempolicy01] Error 1
> make[4]: Leaving directory
> `/home/LTP/ltp-2009-12-08/testcases/kernel/syscalls/get_mempolicy'
> make[3]: *** [all] Error 2
> ------------
>
> For reference, "make" succeeded in my following systems:
>  - RHEL5.4 (kernel 2.6.18-164.el5) and x86 architecture
>  - RHEL5.4 (kernel 2.6.18-164.el5) and x86_64 architecture
>
>
> "nodemask_set" is the structure whitch defined in following two header
> files:
>  (a) "${LTPROOT}/testcases/kernel/syscalls/utils/numaif.h"
>  (b) "/usr/include/numa.h"
>
> In "numaif.h" file, definition is as follows:

Mitani-san,
    This issue keeps on coming back to haunt us. Can you tell me what
the Fedora Core equivalent of RHEL 4.8 is so I can isolate and resolve
the issue?
Thanks,
-Garrett



------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-12-09  7:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-08 10:16 [LTP] Build failure with ltp-2009-12-08 cvs Mitani
2009-12-09  5:06 ` Garrett Cooper
2009-12-09  7:43   ` Mitani [this message]
2009-12-11 13:20     ` Garrett Cooper
2009-12-11  3:47   ` Mitani

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='000401ca78a3$56963f50$03c2bdf0$@co.jp' \
    --to=mitani@ryobi.co.jp \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=yanegomi@gmail.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