dpkg/data, branch master

Merge https://salsa.debian.org/dpkg-team/dpkg

2019-11-26T11:00:30Z

data: Add missing purpose and column description for tupletable

2018-08-30T01:31:03Z

arch: Add support for riscv64 CPU

2018-01-16T10:24:56Z

[guillem@debian.org: - Update unit-tests. ] Closes: #822914 Stable-Candidate: 1.18.x Signed-off-by: Guillem Jover

dpkg (1.19.1~dyson1)

2017-11-19T14:57:02Z

Merge git://anonscm.debian.org/dpkg/dpkg

2017-11-19T11:16:14Z

arch: Add support for ARM64 ILP32

2017-05-07T14:50:08Z

Closes: #824742 Based-on-patch-by: Wookey

data: Do not enable PIE when linking static programs

2016-11-13T17:08:15Z

It seems like at least glibc does not support statically linked PIE programs, and produces random junk. Disable globally for now, if there's a desire to enable static PIE binaries, which is known to work on some architectures (such as musl-based ones) we can add specialized specs files in the future. Closes: #843714 Proposed-by: Szabolcs Nagy

data: Improve PIE handling

2016-11-11T01:34:16Z

- Rename the spec name cc1_options to self_spec. - Do not set PIE options if they have been negated, and do not reset them if they have been requested. Closes: #843791, #843826

Dpkg::Vendor::Debian: Improve PIE flags support

2016-11-07T02:25:46Z

Fix changelog for dpkg 1.18.11 to mention PIE got enabled by default for all architectures, not just the ones where gcc does that itself. When emitting PIE flags on architectures where gcc does not inject those itself, do it via a specs file too, so that maintainers can use them unconditionally regardless of the object being compiled or linked. When injecting -no-pie for linking via gcc specs also inject -fno-PIE. Update the documentation to make the current situation more clear.

Dpkg::Vendor::Debian: Handle PIE enabled by default in gcc

2016-11-06T02:07:14Z

Add support for compiler built-in features, so that we do not set them when enabled and set negated flags when disabled. We use gcc spec files to set these flags so that we avoid any conflict with other incompatible flags that would make the build fail. Closes: #835149 Based-on-patch-by: Bálint Réczey