From: "Mitani" <mitani@ryobi.co.jp>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] make error
Date: Wed, 9 Dec 2009 16:38:16 +0900 [thread overview]
Message-ID: <000001ca78a2$93fd5a50$bbf80ef0$@co.jp> (raw)
Hi,
Sorry, I don't know how to response to following thread:
"http://www.mail-archive.com/ltp-list@lists.sourceforge.net/msg08965.html"
but I want to comment it:
> > On Thursday 12 November 2009 01:20:37 yali_ning wrote:
> > > I came across an error , when compiling the ltp-20091030. the step
> > is :
> > >
> > > gcc -Wall -g -Os -g -O2 -fno-strict-aliasing -pipe -Wall
> > >
> > -I/mnt/sdb1/nly1/ltp-1030/ltp-full-20091031/testcases/kernel/include
> > > -I../../../../include -I../../../../include -L../../../../lib
> > vfork.c
> > > -lltp -o vfork In file included from /usr/include/asm/ptrace.h:58,
> > > from /usr/include/linux/ptrace.h:49,
> > > from vfork.c:45:
> > > /usr/include/asm/fpu.h:57: error: redefinition of 'struct
> > ia64_fpreg'
> > > In file included from /usr/include/linux/ptrace.h:49,
> > > from vfork.c:45:
> > > /usr/include/asm/ptrace.h:208: error: redefinition of 'struct
> > > pt_all_user_regs'
> >
> > this should be fixed already in latest cvs
> > -mike
> No, I tried to install latest cvs version under RHEL5.4 on a ia64
> machine but the same error still existed.
>
> What puzzled me is, it said it was the redefinition-error, but I
> couldn't even find the originally defined structs.
>
> Thanks,
> Caspar
============
Well, I think that the report that Caspar says is right.
I tried to "make" with "ltp-2009-12-08" version
in RHEL5.4 (kernel 2.6.18-164.el5) and ia64 architecture, too.
But it output the error message same as Caspar's report
and ended in failure.
And same failure occurred in "ltp-full-20091031.tgz" version, too.
I tried various versions until now.
LTP version --- error occurred in...
---------------------------------------------------------------------
(1) ltp-full-20091031 --- "vfork.c" (This failure)
(2) ltp-2009-11-17 --- "vfork.c" (Resembles this failure)
(3) ltp-2009-11-19 --- "vfork.c" (Resembles this failure)
(4) ltp-2009-11-24 --- "vfork.c" (Resembles this failure)
(5) ltp-2009-11-26 --- "vfork.c" (Resembles this failure)
(6) ltp-2009-11-27 --- "pidns03.c" (Before than this failure)
(7) ltp-2009-11-30 --- "pidns03.c" (Before than this failure)
(8) ltp-2009-12-01 --- "libclone.c" (Before than this failure)
(9) ltp-2009-12-02 --- "libclone.c" (Before than this failure)
(10) ltp-full-20091130 --- "libclone.c" (Before than this failure)
(11) ltp-2009-12-07 --- "vfork.c" (This failure)
(12) ltp-2009-12-08 --- "vfork.c" (This failure)
Thank you--
-Tomonori Mitani
------------------------------------------------------------------------------
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
next reply other threads:[~2009-12-09 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 7:38 Mitani [this message]
2009-12-09 7:48 ` [LTP] make error Garrett Cooper
2009-12-09 11:09 ` Mike Frysinger
2009-12-09 12:05 ` Mike Frysinger
[not found] <862970112.6041260277607150.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com>
2009-12-08 13:07 ` Caspar Zhang
2009-12-11 14:25 ` Garrett Cooper
-- strict thread matches above, loose matches on Subject: below --
2009-11-12 6:20 yali_ning
2009-11-13 3:31 ` Mike Frysinger
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='000001ca78a2$93fd5a50$bbf80ef0$@co.jp' \
--to=mitani@ryobi.co.jp \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.