We generate all config files when building linux-source-<version>,
and this requires running kconfig. kconfig is now built using
bison and flex instead of requiring their output to be already
included in the source tree.
libelf-dev is needed to build objtool when CONFIG_STACK_VALIDATION
and CONFIG_UNWINDER_ORC are enabled, which is currently the case.
Do not mark it as !nopython !pkg.linux.notools otherwise the build
will fail in a minimal chroot (pbuilder/etc).
libbabeltrace-ctf-dev was merged into libbabeltrace-dev, so the
build dependencies are unsatisfiable in unstable. For stretch-
backports we will still want both of them. So add a suitably
versioned dependency on libbabeltrace-dev as a preferred
alternative to libbabeltrace-ctf-dev.
The dpkg bugs affecting libssl-dev build deps were fixed in 1.18.8.
The various non-M-A packages for which we used :native qualification
were fixed before stretch release. So neither unstable nor
stretch-backports needs these.
It has finally been removed after all docs were converted to ReST format.
As there is no longer a way to build manpages, remove the linux-manual
package.
Listing usr/sbin in linux-cpupower.install caused FTBFS on !x86 as
cpupower itself doesn't install anything there. Do the architecture
filtering in the debhelper lists instead of complicating
debian/rules.real further.
The new versions have Multi-Arch: allowed, and surprisingly dpkg doesn't
consider them to satisfy a dependency on openssl:native. Change the
build-dependency into an alternative satisfiable by both old and new
versions. (Closes: #839145)
- Add python-sphinx and python-sphinx-rtd-theme to Build-Depends-Indep
- Install files from both HTML output directories into the package
- Exclude RST sources from the package
Currently the linux-source-<version> package may or may not include
these files, depending on the order things are built in.
As autotools always modifies the source directory, copy (rsync) the
source to the build directory and build in-place there.
Currently we build-depend on the native python (via asciidoc), and on
the host python (via python-dev). As these are not coinstallable it
is impossible to perform a complete cross-build. Until that's resolved,
this will allow cross-building of most of the package with the
combination of the 'cross' and 'nopython' profiles.
(This also sidesteps the issue of perf wanting a multilib compiler.)
The current cross-compiler packages don't set the Multi-Arch field, so
specify that the cross-compiler package must be native, rather than any
architecture.
flex doesn't support multi-arch, and this would require splitting it
(#611230, #761449). Force use of the native package for now.
openssl doesn't support multi-arch but probably easily could (#827028).
Force use of the native package for now.
We need the native libssl-dev while building the kernel itself and the
host libssl-dev while building tools for linux-kbuild.
Document the state of cross-building in README.source.
The list is getting hard to read as we add build profiles. It's also easier
to merge and cherry-pick changes when each dependency is on a separate line.
* Drop redundant gitignore.patch from linux-tools
* Rename linux-tools' debian/templates/control.main.in to
debian/templates/control.tools.in
* Combine changelogs, putting all entries for each upstream release
cycle in chronological order
* Combine rules and gencontrol.py code
Karsten did a test-build on armhf and found failures due to missing modules
and directories.
* The wireless drivers from staging need to be optional; this requires
support for wildcards in optional-inclusion lines
* The check for a containing directory must only be done for non-optional
inclusion lines
Bump the kernel-wedge version requirement and add the optional-include
suffixes.
Currently we have xz-utils in build-depends-indep as we explicitly
use xz to compress files in linux-source. We also have a build-
dependency on lzma (now a virtual package provided by xz-utils),
but only on armel which was the first architecture for which we
set CONFIG_KERNEL_XZ=y.
However, since 3.7 we've set CONFIG_KERNEL_XZ for all architectures so
xz-utils is needed everywhere. Currently we get away with this
because dpkg-dev depends on xz-utils, but this could change in future.
Build-depend on xz-utils without qualification.