On 2016-10-07 09:23, Andreas Beckmann wrote:
> should be fixed in git
New version with PIE enabled uploaded to sid, thanks for all your input!
Andreas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 2016-10-07 07:05, Graham Inggs wrote:
> ...but then ended up with a bunch of undefined references building
> python/src/perfmon_int_wrap.c which seem to be SWIG-related.
... because LDFLAGS contains -pie, but we build a .so ...
should be fixed in git
Andreas
--
You received this bug
I managed to get a bit further with the following patch:
--- a/lib/Makefile
+++ b/lib/Makefile
@@ -33,7 +33,7 @@
SRCS += pfmlib_perf_event_pmu.c pfmlib_perf_event.c pfmlib_perf_event_raw.c
endif
-CFLAGS+=-D_REENTRANT -I. -fvisibility=hidden
+CFLAGS+=-D_REENTRANT -I. -fvisibility=hidden -fPIC
On 2016-10-06 22:27, Steve Langasek wrote:
>> /usr/bin/ld: pfmlib_common.lo: relocation R_X86_64_PC32 against symbol
>> `stderr@@GLIBC_2.2.5' can not be used when making a shared object; recompile
>> with -fPIC
>> /usr/bin/ld: final link failed: Bad value
>> collect2: error: ld returned 1 exit
On Thu, Oct 06, 2016 at 06:59:10PM -, Graham Inggs wrote:
> @anbe:
> > if I drop ,-pie I get an FTBFS:
> I get the same in Ubuntu, building in a PPA.
The package currently in Ubuntu yakkety does not FTBFS in this way with
-fPIE, so this is a regression. And since PIE is a security feature,
@anbe:
> if I drop ,-pie I get an FTBFS:
I get the same in Ubuntu, building in a PPA.
@vorlon:
Are there any particular commits, listed in comment #4, that you are concerned
about?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 2016-10-04 08:27, Andreas Beckmann wrote:
>> +# see FEATURE AREAS in dpkg-buildflags(1)
>> +export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-pie
>>
>> This explicitly disables PIE, which is enabled by default on amd64 and
>> s390x in yakkety. Why should we want to disable PIE? There's no
>>
For reference, these are the commits between 4.7.0+git11-gbfb9baf-1 and
4.7.0+git30-gd422ba2-1.
(Newest at the top)
[d422ba2] fix Intel Goldmont offcore_response average latency support
[ef73810] Add support for Intel Knights Landing core PMU
[359a11a] allow . as a delimiter for event strings
On 2016-10-03 23:10, Steve Langasek wrote:
> The new libpfm4 version seems to include changes besides just adding new
> code for enabling the new CPUs, and it's non-trivial to see from source
> review what impact this may have on existing uses. Could we have some
> analysis of these changes, and
The new libpfm4 version seems to include changes besides just adding new
code for enabling the new CPUs, and it's non-trivial to see from source
review what impact this may have on existing uses. Could we have some
analysis of these changes, and their potential risk to the release?
There's also
The papi FFe looks straightforward, granted.
** Changed in: papi (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629989
Title:
FFe: Sync libpfm4
11 matches
Mail list logo
