Pass $(CROSS_COMPILE) or host GNU type through to upstream build rules.
debian/rules.real: Filter tools packages by host arch, not build arch
debian/rules.d/Makefile: Build the tools needed for headers_install in
a separate subdirectory
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.
Martin Michlmayr found that userland builds fail if 'uname -m' reports
the native kernel architecture, and that's because we don't explicitly
set ARCH for the headers_install target. That's fine for most cases
of a 32-bit chroot on a 64-bit kernel because a single source
architecture covers both, but arm/arm64 is an exception.
This doesn't make actual cross-builds of userland tools work.
Enable some options used by the Jetson TX1 board. MAX77620 is used
as system PMIC and PCA9539 as I2C GPIO bus expander.
Set I2C=y since this is required by MFD_MAX77620.
CONFIG_GPIO_MAX77620 and CONFIG_GPIO_MAX77620 are not upstream yet
but will be. I'm adding the options now to make the commit cover
everything needed.
This is patched on a patch submitted upstream by Laxman Dewangan.
These packages will be taken over by src:linux-signed. Still do
everything but building the packages so we find configuration
errors before building linux-signed.
BLK_DEV_FD has *never* been enabled on any of these architectures!
The old arm/footbridge configuration did enable it and this suggestion
seems to be have been thoughtlessly copied over to these other
architectures.
linux-kernel-headers was removed from unstable in 2007, so presumably
was last released in etch.
libkxl0-dev still depends on it, so don't remove the Provides yet.
Previously each tarball would be uploaded to .../rt/<upstream-version>/
and then later moved to .../rt/<upstream-version>/older/. Now they are
appearing in .../older/ immediately so we can construct stable URLs
under there.
Ben Hutchings
Salvatore Bonaccorso
Aurelien Jarno
Martin Michlmayr