public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Caspar Zhang <czhang@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] fix compiling error on ia64 platform (ltp-full-20091130)
Date: Fri, 18 Dec 2009 13:27:00 -0500	[thread overview]
Message-ID: <200912181327.01697.vapier@gentoo.org> (raw)
In-Reply-To: <2039563304.268931260765372686.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com>


[-- Attachment #1.1: Type: Text/Plain, Size: 1065 bytes --]

On Sunday 13 December 2009 23:36:12 Caspar Zhang wrote:
> ----- "Mike Frysinger" <vapier@gentoo.org> wrote:
> > On Friday 11 December 2009 06:30:01 Caspar Zhang wrote:
> > >   Here are two patches to fix compiling error in ia64,
> > > I tested only in version ltp-full-20091130, please check
> > > your own version. They are for work well on my system.
> > > See the attachment.
> >
> > the ia64 change is incorrect.  there's ia64 ifdef hacks in there
> > already which
> > are to be used.
> 
> the ia64 ifdef hacks in 20091130 are the following lines(in file
> ptrace.h):
> 
>     17	/* ia64's a real pain.. */
>     18	#if defined(__ia64__)
>     19	#undef FU_ia64_fpreg
>     20	#undef FU_pt_all_user_regs
>     21	#if ! defined(ia64_fpreg)
>     22	# define ia64_fpreg FU_ia64_fpreg
>     23	#endif
>     24	#if ! defined(pt_all_user_regs)
>     25	# define pt_all_user_regs FU_pt_all_user_regs
>     26	#endif
>     27	#endif
> 
> I don't think these codes could sovle the compiling problem.

they do if they're used right
-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

  reply	other threads:[~2009-12-18 18:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1117953467.268911260765366627.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com>
2009-12-14  4:36 ` [LTP] [PATCH] fix compiling error on ia64 platform (ltp-full-20091130) Caspar Zhang
2009-12-18 18:27   ` Mike Frysinger [this message]
2009-12-15  6:14 Mitani
2009-12-15 19:39 ` Garrett Cooper
2009-12-18 18:21   ` Mike Frysinger
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] <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=200912181327.01697.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=czhang@redhat.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