From: than <than@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: benh@kernel.crashing.org, mpe@ellerman.id.au,
"Dan Horák" <dhorak@redhat.com>
Subject: no 32-bit support on LE powerpc64le
Date: Tue, 02 Jun 2015 16:28:53 +0200 [thread overview]
Message-ID: <556DBDA5.2000209@redhat.com> (raw)
Hello all,
we have a problem to build kernel-4.0 on ppc64le. The real problem is
that there's no 32 bit code generator support in gcc on the ppc64le.
So the option NO_PERF_READ_VDSO32 should be set to 1 on ppc64le.
I have create a patch which fixes the issue for me.
diff -Nur linux-4.0/tools/perf/config/Makefile.than linux-4.0/tools/perf/config/Makefile
--- linux-4.0/tools/perf/config/Makefile.than 2015-06-02 11:58:17.525763988 +0200
+++ linux-4.0/tools/perf/config/Makefile 2015-06-02 12:31:04.898865043 +0200
@@ -642,6 +642,9 @@
CFLAGS += -DHAVE_KVM_STAT_SUPPORT
endif
+ifeq ($(ARCH),ppc64le)
+ NO_PERF_READ_VDSO32 := 1
+endif
ifeq (${IS_64_BIT}, 1)
ifndef NO_PERF_READ_VDSO32
$(call feature_check,compile-32)
For more infos please take a look at
https://bugzilla.redhat.com/show_bug.cgi?id=1227260
Thanks,
Best Regards,
Than
reply other threads:[~2015-06-02 14:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=556DBDA5.2000209@redhat.com \
--to=than@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=dhorak@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
/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.