This is based on the ARCv2 32-bit little-endian hard-float ISA.

Closes: #980963
Based-on-patch-by: Alexey Brodkin <Alexey.Brodkin@synopsys.com>

There are better memory leak and overflow detector tools around, there
is no need for this ad-hoc implementation that might not detect memory
misuse anyway.

Changelog: internal

On AIX we need to use getprocs64() to fetch the current program name.

Changelog: porting

On at least AIX fsync(3) requires a writable file descriptor, which
opendir(3) does not provide. But even with a writable file descriptor
fsync(3) does not always work on directories.

Disable all directory fsync()s if the system does not support it.

This reduces boirlerplate code.

This also covers the case of found in the system libraries, which we
cover later anyway, so the assignment here is confusing.

On Solaris the socket functions are not found on libc but on libsocket.
We need those for start-stop-daemon.

On systems such as macOS and AIX this macro is not defined. Just set it
to 0 so that we can compile the sources.

Changelog: porting

[guillem@debian.org: Hook into build system. ]

Closes: #986103
Signed-off-by: Guillem Jover <guillem@debian.org>

When deciding whether to de-configure a package due to Breaks we print
a message stating so, as well as when we are actually de-configuring
them. When deciding whether to remove a package due to Conflicts we also
print a message, but were not printing anything when removing these
package which seems rather confusing and makes the installation non
obvious.

Closes: #985401

This should make it easier to see what each does.

These are widely considered weak by current standards, and have had
successful attacks performed on them.

The generic die() messages are not very helpful.

This new setting, disabled by default, enables the Link Time
Optimization.

Closes: #940571

We should not be repeating the same assignment all over the place for
compiler flag names.

We have other classes in the same directory, and should check whether
the format is really a Dpkg::Changelog object.

When we are trying to patch a file that is not present in the original
tarball, the error message is rather confusing, as it mentions possible
fuzz problems, as if the file existed, which might mislead the user.

Add a hint to check whether the file is present in the original tarball
to avoid leading the user into dead ends.

Ideally the affected tarball would be reported in the error message, but
that information is currently not available on that code path.

Reported-by: Joseph Nahmias <jello@debian.org>

When the changelog shows a source package rename, but no version change,
we also need to include the orig tarball.

Closes: #980066

The entries are used in a first fully match order, so the regular
expressions need to be listed from most specific to less specific
when using wildcards.

The architectures need to have the bijective property when converting
back and forth from the Debian arch name to the GNU triplet. Enforce
this in the test suite to make it easier to guarantee this when adding
new architectures to the tables.

We execute the same makefile with different environments, so we need
some description to distinguish them in case they fail, otherwise it
is too confusing to diagnose.

Avoid using things we are still testing, instead of the system modules,
and for consistency with the rest of the perl unit tests.

Even though the codebase is not threaded, the former is a safe function
and we should be using it to be future-proof.

Changelog: internal
Warned-by: lgtm

This is an explicit behavior that we might consider changing, but it's
not a bug per-se.

Changelog: internal
Warned-by: lgtm

These are behavior we implement for workarounds or robustness parsing,
which we should probably not even plan on removing, as that would leave
manually edited files open to breakage.

Changelog: internal
Warned-by: lgtm

These are not bugs per-se, just things to perform at some point.

Changelog: internal
Warned-by: lgtm

Changelog: internal
Warned-by: lgtm

These variables are handled by autoconf, and there's no need to set them
ourselves.

The Perl version in Debian buster is 5.28.1, which is the release that
will be oldstable once 1.21.x gets uploaded to Debian unstable.

[guillem@debian.org: Hook into build system. ]

Signed-off-by: Guillem Jover <guillem@debian.org>

Signed-off-by: Guillem Jover <guillem@debian.org>

Signed-off-by: Guillem Jover <guillem@debian.org>

Changelog: silent

We should ignore any builtin build dependencies (in particular
build-essential, which is an arch:any package), as we are forcing the
build and host architectures, which will make them not match whatever
is on the system status file if present at all, and cause dependency
unsatisfiability.

Fixes: commit 0e2ae4e7