Package: libpgm / 5.2.122~dfsg-3

Metadata

Package Version Patches format
libpgm 5.2.122~dfsg-3 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
hurd ftbfs fix.patch | (download)

openpgm/pgm/configure.ac | 6 5 + 1 - 0 !
1 file changed, 5 insertions(+), 1 deletion(-)

---
force running benchmark in case tsc_mhz returns 0.patch | (download)

openpgm/pgm/time.c | 19 14 + 5 - 0 !
1 file changed, 14 insertions(+), 5 deletions(-)

 [patch] time.c: force running benchmark in case tsc_mhz returns 0 from /proc/cpuinfo
support_source_date_epoch.patch | (download)

openpgm/pgm/version_generator.py | 5 3 + 2 - 0 !
1 file changed, 3 insertions(+), 2 deletions(-)

 add support for source_date_epoch
 Allow one to override the recorded build time by setting SOURCE_DATE_EPOCH
 in the environment. More details can be found on:
 https://reproducible-builds.org/specs/source-date-epoch/
pkg config do not add I to non existing directory.patch | (download)

openpgm/pgm/openpgm-5.2.pc.in | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 pkg-config: do not add -i to non-existing directory
 foo/lib/pgm-5.2/include does not exist, so applications using strict
 compiler flags will fail to build due to this -I flag
reproducible architecture.patch | (download)

openpgm/pgm/version_generator.py | 7 6 + 1 - 0 !
1 file changed, 6 insertions(+), 1 deletion(-)

 version_generator.py: make build reproducible
 If SOURCE_DATE_EPOCH is defined then the user is most likely interested
 in building the library in a reproducible way. So in that case use fixed
 "BuildSystem" and "BuildMachine" strings instead of the operating system
 and architecture.