linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
	rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
	fweisbec@gmail.com, oleg@redhat.com, joel@joelfernandes.org,
	Willy Tarreau <w@1wt.eu>,
	"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>
Subject: [PATCH tip/core/rcu 5/8] rcutorture: Always strip using the cross-compiler
Date: Sun, 11 Nov 2018 12:01:40 -0800	[thread overview]
Message-ID: <20181111200143.10177-5-paulmck@linux.ibm.com> (raw)
In-Reply-To: <20181111200127.GA9511@linux.ibm.com>

From: Willy Tarreau <w@1wt.eu>

Strip using -s on the compiler command line instead of calling the "strip"
utility as the latter isn't necessarily compatible with the target arch.

Signed-off-by: Willy Tarreau <w@1wt.eu>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
---
 tools/testing/selftests/rcutorture/bin/mkinitrd.sh | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/tools/testing/selftests/rcutorture/bin/mkinitrd.sh b/tools/testing/selftests/rcutorture/bin/mkinitrd.sh
index 70661457e3d6..dbb6f0160281 100755
--- a/tools/testing/selftests/rcutorture/bin/mkinitrd.sh
+++ b/tools/testing/selftests/rcutorture/bin/mkinitrd.sh
@@ -113,8 +113,7 @@ int main(int argc, int argv[])
 	return 0;
 }
 ___EOF___
-${CROSS_COMPILE}gcc -static -Os -o init init.c
-strip init
+${CROSS_COMPILE}gcc -s -static -Os -o init init.c
 rm init.c
 echo "Done creating a statically linked C-language initrd"
 
-- 
2.17.1


  parent reply	other threads:[~2018-11-11 20:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-11 20:01 [PATCH tip/core/rcu 0/8] Automate initrd generation for v4.21/v5.0 Paul E. McKenney
2018-11-11 20:01 ` [PATCH tip/core/rcu 1/8] rcutorture: Automatically create initrd directory Paul E. McKenney
2018-11-11 20:01 ` [PATCH tip/core/rcu 2/8] rcutorture: Add initrd support for systems lacking dracut Paul E. McKenney
2018-11-11 20:01 ` [PATCH tip/core/rcu 3/8] rcutorture: Make initrd/init execute in userspace Paul E. McKenney
2018-11-11 20:01 ` [PATCH tip/core/rcu 4/8] rcutorture: Add cross-compile capability to initrd.sh Paul E. McKenney
2018-11-11 20:01 ` Paul E. McKenney [this message]
2018-11-11 20:01 ` [PATCH tip/core/rcu 6/8] rcutorture: Check initrd/init instead of initrd only Paul E. McKenney
2018-11-11 20:01 ` [PATCH tip/core/rcu 7/8] rcutorture: Import a copy of nolibc Paul E. McKenney
2018-11-11 20:01 ` [PATCH tip/core/rcu 8/8] rcutorture: Make use of nolibc when available Paul E. McKenney

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=20181111200143.10177-5-paulmck@linux.ibm.com \
    --to=paulmck@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=edumazet@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=w@1wt.eu \
    /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;
as well as URLs for NNTP newsgroup(s).