| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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 <nsz@port70.net>
|
|
- 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
|
|
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.
|
|
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 <balint@balintreczey.hu>
|
|
This allows to detangle the libc used from the calling conventions.
|
|
This should allow external parsers to know if they can understand the
table contents.
|
|
|
|
|
