From: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Linux perf users list <linux-perf-users@vger.kernel.org>,
Linux s390 list <linux-s390@vger.kernel.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Thomas Richter <tmricht@linux.vnet.ibm.com>,
jonathan.hermann@de.ibm.com, kernel-team@lge.com,
jolsa@kernel.org
Subject: Re: [PATCH] perf s390: always build with -fPIC
Date: Fri, 1 Dec 2017 15:12:45 +0100 [thread overview]
Message-ID: <20171201141245.GD6452@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171201021709.GB30867@sejong>
Hi Namhyung,
On Fri, Dec 01, 2017 at 11:17:09AM +0900, Namhyung Kim wrote:
> On Thu, Nov 30, 2017 at 09:49:25AM +0100, Hendrik Brueckner wrote:
> > On s390, object files must be compiled with position-indepedent code
> > in order to be incrementally linked or linked to shared libraries.
> > Therefore, add -fPIC to the CFLAGS for s390 to ensure each object
> > file is built properly.
>
> Could you please tell me what was the actual problem? I guess this is
> somewhat related to the Jiri's Fedora build fix.
Building, linking of perf did not work (I think it was on a Fedora 27)
resulting in an error message like:
/usr/bin/ld: perf-in.o: `__printf_chk@@GLIBC_2.4' non-PLT reloc for symbol
defined in shared library and accessed from executable (rebuild file with
-fPIC ?)
/usr/bin/ld: final link failed: Bad value
On s390, objects must be compiled with -fPIC when used for shared object
or position-indendepent executables (PIE). In doubt, it is better to
build with -fPIC (there are no performance degration).
Thanks and kind regards,
Hendrik
prev parent reply other threads:[~2017-12-01 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 8:49 [PATCH] perf s390: always build with -fPIC Hendrik Brueckner
2017-12-01 2:17 ` Namhyung Kim
2017-12-01 14:12 ` Hendrik Brueckner [this message]
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=20171201141245.GD6452@linux.vnet.ibm.com \
--to=brueckner@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=heiko.carstens@de.ibm.com \
--cc=jolsa@kernel.org \
--cc=jonathan.hermann@de.ibm.com \
--cc=kernel-team@lge.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=tmricht@linux.vnet.ibm.com \
/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.