Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
This should speed up compression on multicore systems. This code has
only been build tested against latest xz-utils git tree, but not run
tested, as the package in Debian is too old. Rrquires xz >= 5.2.0.
|
|
The option --disable-devel-docs can be used to override the current
default, which is to build development documentation.
|
|
This fixes a build failure on at least FreeBSD, and possibly other
BSD systems, where the md5.h header provided by libmd maps the md5
functions to namespaced ones, and then there is a mismatch between
the always included functions from libcompat and from libmd.
|
|
Warn on features not present in ISO C99 but present in ISO C11,
on sizeof for an array argument, on switch keyword with bool
values, and logical not on the left handside of a comparison.
|
|
This flag does not work anymore in gcc 5 w/o also passing -Wformat.
|
|
We are only checking if the va_copy symbol is available, do not try to
run the test program.
|
|
SUSv2 and earlier had conflicting semantics with the C99 snprintf()
ones. Because we expect a C99 environment, assume that if we are using
SUSv3 or newer then we have a working snprintf() implementation.
|
|
Use the opportunity to fix the indentation.
|
|
We enable -Werror when checking the flags so that on compilers like
clang which just emit a warning on unknown warning options, instead
of erroring out, we get proper detection.
We could just use stuff like -Werror=unknown-warning-option and
-Werror=unused-command-line-argument, but then we would need to detect
if those are available as they might make the compiler error out if
they are no supported. So just using the blanket -Werror, although more
broad, makes the code less complicated.
|
|
These are deprecated symbols, and some systems which do have strerror()
do not have these variables, most notably GNU/Hurd. So do not try to test
the current implementation there as it will fail.
Closes: #758199
|
|
If we are not using libselinux, then we cannot build the selinux
compatibility code as it requires the library. Also fixes build failures
on non-Linux systems, where the library is not available.
Closes: #757637
|
|
This is now a fallback implementation in case libselinux is too old.
|
|
There's no point in duplicating all this code in dpkg, when this is
provided now by libselinux.
|
|
|
|
|
|
|
|
This makes it possible to embed libcompat inside libdpkg, so that the
static library that we ship is self contained with the required
compatibility code, specifically the MD5 functions.
This also prepares the build system for when we start building a
shared library, although it disables it by default.
Closes: #746122
|
|
Noticed while investigating the lack of branch coverage. It appears the
option is supported for a very long time, at least since gcc 4.1.x.
|
|
And clarify the comment on the designated initializers.
|
|
This allows for non-GNU systems to use another value for their GNU tar,
which usually is either gnutar or gtar.
|
|
These libraries are not used now, and the linking is unnecessary and
superfluous.
The libps interfaces used to expose or required the caller to use
functions from those other libraries long time ago, not anymore though.
|
|
It is way more descriptive, and has a better type. Check for C++11
compiler support and fallback nullptr to 0 if unavailable.
|
|
Specify the current compiler being used, and shorten the message
checking for an option to enable C99 support.
|
|
This fixes a build failure with old g++ compilers not accepting
-Wc++11-compat.
|
|
|
|
The ncurses bug (#542031) has long been fixed.
|
|
This will allow downstreams to choose something better than gzip as
their default compressor, for example xz. Or when xz becomes the
default to revert back to something else.
|
|
|
|
Use liblzma if available instead of external commands to handle .xz
and .lzma compressed files.
Among other things, this means the xz-utils package no longer has to
be part of the base system.
Based-on-patch-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
This sets up the environment to be able to run the local scripts using
local modules and data files.
|
|
The standard way to select if a specific component of the build is to
be enabled or disabled is through --enable-foo and --disable-foo
options, --with-foo and --without-foo are used for selecting external
modules to be used.
|
|
|
|
The md5 module imported from OpenBSD is using these BSD types, but
those are not present on at least Solaris. Define them to their
corresponding C99 types, so that the imported code has to be modified
as less as possible.
Reported-by: Andrew Stormont <andrew.stormont@nexenta.com>
|
|
When building a distribution tarball, the full gettext suite is required
because the *.gmo files are shipped in there. A lex program is also
required because the tarball ships the pre-generated *.c files.
Reported-by: Cyril Brulebois <kibi@debian.org>
|
|
Reported-by: Cyril Brulebois <kibi@debian.org>
|
|
The variable is declared as precious via AC_ARG_VAR, but assigned to
unconditionally.
|
|
The build system requires a perl interpreter to retrieve its library
directory path and to execute dpkg-architecture.pl.
|
|
Continuing will only produce a buggy dpkg.
|
|
This will help building dpkg on systems where perl is not at
/usr/bin/perl, which we were already taking into consideration for the
resulting scripts but not during build.
|
|
|
|
We use those to create binary output, so we require them to be working.
|
|
|
|
Using sync() on unpack causes _all_ filesystems to be sync'd, which is
not so great when one of those is a thumb drive, mounted over a network,
or otherwise slow. Remove the sync-instead-of-fsync codepath due to
those side-effects and to simplify maintenance.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Reported-by: Raphael Geissert <geissert@debian.org>
Tested-by: Raphael Geissert <geissert@debian.org>
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Conflicts:
debian/changelog
m4/dpkg-funcs.m4
man/dpkg.1
|
|
It causes undesired I/O on unrelated file systems. It also makes the
code behave differently on Linux systems.
Allow the possibility to enable it again for the benefit of downstreams,
which might want to use it regardless of its problems. Although this
code path will most probably be removed in the near future.
Closes: #588339, #595927, #600075
|
|
Remove trailing spaces. Remove blank lines not separating different code
blocks. Remove blank lines at the end of the file.
|
|
Global review, which includes the following changes to try to increase
consistency, update and improve the source code comments:
- Spelling fixes.
- Use American English forms.
- Uppercase NULL, NUL and ASCII.
- Use “Note: ” instead of the slightly cryptic “NB: ” form.
- Write comments as proper sentences, including capitalizations and
ending dots.
- Move comments before the code, function or variable they refer to.
- Move general function comments outside the body.
- Convert function and variable description comments to doxygen.
- Use one space before dot, exclamation and question marks.
- Use ‘’ or “” instead of `' style quoting.
- Remove author names from comments, already visible from “git blame”.
- Mark strings for translators with “TRANSLATORS: ”.
- Remove useless or outdated comments.
- Fix comment indentation.
- Standardize comment format:
/* Short text comment. */
/* Long text,
* comment. */
/*
* Section text.
*/
|