All of lore.kernel.org
 help / color / mirror / Atom feed
From: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP]  [PATCH] ldd01: using 'ppc' to check powerpc arch
Date: Thu, 11 Sep 2014 10:27:09 +0800	[thread overview]
Message-ID: <20140911022709.GA16027@localhost.localdomain> (raw)

Hello,
The ldd01 always failed on some powerpc systems of ours. I have figured
out a patch. Please take a look. Thanks in advance.


On some powerpc system, the 'uname -a' doesn't show 'powerpc' but will
show 'ppc'. So we need using it to check the powerpc arch.

Signed-off-by: Han Pingtian <hanpt@linux.vnet.ibm.com>
---
 testcases/commands/ade/ldd/ldd01 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/testcases/commands/ade/ldd/ldd01 b/testcases/commands/ade/ldd/ldd01
index c60d3ac..569902e 100755
--- a/testcases/commands/ade/ldd/ldd01
+++ b/testcases/commands/ade/ldd/ldd01
@@ -47,7 +47,7 @@ do_setup()
 	mkdir $TCtmp
 
 	# Check for ppc64 architecture or x86_64 architecture
-	if uname -a | grep -iq powerpc; then
+	if uname -a | grep -iq 'ppc\|powerpc'; then
 		file lddfile1.obj | grep 64-bit >/dev/null 2>&1
 		if [ $? -eq 0 ]; then
 			CFLAGS="-m64"
-- 
1.9.3


------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

             reply	other threads:[~2014-09-11  2:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11  2:27 Han Pingtian [this message]
2014-09-11 11:23 ` [LTP] [PATCH] ldd01: using 'ppc' to check powerpc arch Poornima Nayak
2014-09-11 14:41 ` Jan Stancek
2014-09-12  7:28   ` Han Pingtian
2014-09-12  8:15     ` Jan Stancek
2014-09-13  2:24       ` Han Pingtian

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=20140911022709.GA16027@localhost.localdomain \
    --to=hanpt@linux.vnet.ibm.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 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.