From: Mike Frysinger <vapier@gentoo.org>
To: ltp-list@lists.sourceforge.net
Cc: Mitani <mitani@ryobi.co.jp>
Subject: Re: [LTP] [PATCH] fix compiling error on ia64 platform (ltp-full-20091130)
Date: Fri, 18 Dec 2009 13:21:09 -0500 [thread overview]
Message-ID: <200912181321.11305.vapier@gentoo.org> (raw)
In-Reply-To: <364299f40912151139s38bd457eg88c6908d805f6ab4@mail.gmail.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 1820 bytes --]
On Tuesday 15 December 2009 14:39:24 Garrett Cooper wrote:
> On Mon, Dec 14, 2009 at 10:14 PM, Mitani wrote:
> > I applied following Casper's patch to "ltp-2009-12-10" cvs,
> > then "make" succeeded in RHEL5.4 ia64 system:
> > http://www.mail-archive.com/ltp-list@lists.sourceforge.net/msg08991.html
> >
> > On the other hand, I used Repository's following sources,
> > but "make" failed.
> > - "ptrace.h" (Revision 1.9)
> > - "ptrace04.c" (Revision 1.13)
> >
> > But, at least, I think that the Repository's revision about "ptrace04.c"
> > is right. And "ptrace04.c" of "ltp-2009-12-15" cvs is same one.
> >
> >
> > Today, I arranged Casper's "ptrace.h" patch for "ltp-2009-12-15" cvs
> > and applied it to this cvs, and "make" succeeded.
> >
> >
> > I tried following other systems as using this patch, and succeeded:
> > - RHEL5.4(kernel : 2.6.18-164.el5) and x86 architecture
> > - RHEL5.4(kernel : 2.6.18-164.el5) and x86_64 architecture
> > - RHEL4.8(kernel : 2.6.9-89.ELsmp) and x86 architecture
>
> Until this issue is resolved (I ran into problems trying to use
> crossdev, so I'll have to manually inspect headers after I track down
> which versions are used in the Redhat distros specified), please
> remember that you _can_ always comment out the line which says:
>
> /* Define to 1 if you have the <asm/ptrace.h> header file. */
> #define HAVE_ASM_PTRACE_H 1
>
> Actually, I think I'll just remove that header check if the build
> passes unless Mike objects, because we really shouldn't be
> #include'ing asm/* headers without having a good reason to do so
> because it results in pain of this magnitude...
the linux/asm ptrace headers are the only place where register defines are
found. the C library ptrace only includes common ptrace requests.
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 390 bytes --]
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
[-- Attachment #3: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-12-18 18:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 6:14 [LTP] [PATCH] fix compiling error on ia64 platform (ltp-full-20091130) Mitani
2009-12-15 19:39 ` Garrett Cooper
2009-12-18 18:21 ` Mike Frysinger [this message]
2009-12-18 18:31 ` Mike Frysinger
2009-12-19 5:10 ` Garrett Cooper
2009-12-19 12:55 ` Mike Frysinger
2010-01-16 23:56 ` Garrett Cooper
[not found] <1117953467.268911260765366627.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com>
2009-12-14 4:36 ` Caspar Zhang
2009-12-18 18:27 ` Mike Frysinger
[not found] <733784191.211351260530878824.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com>
2009-12-11 11:30 ` Caspar Zhang
2009-12-11 20:04 ` 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=200912181321.11305.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=mitani@ryobi.co.jp \
/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