linux-toradex.git/scripts/package/mkdebian, branch v5.5-rc3

scripts: package: mkdebian: add missing rsync dependency

2019-12-17T10:23:10+00:00

We've missed the dependency to rsync, so build fails on
minimal containers.

Fixes: 59b2bd05f5f4 ("kbuild: add 'headers' target to build up uapi headers in usr/include")
Signed-off-by: Enrico Weigelt, metux IT consult 
Signed-off-by: Masahiro Yamada

builddeb: generate multi-arch friendly linux-libc-dev package

2019-07-17T01:25:10+00:00

Debian-based distributions place libc header files in a machine
specific directory (/usr/include/) instead of
/usr/include/asm to support installation of the linux-libc-dev
package from multiple architectures. Move headers installed by
"make headers_install" accordingly using Debian's tuple from
dpkg-architecture (stored in debian/arch).

Signed-off-by: Cedric Hombourger 
Signed-off-by: Masahiro Yamada

kbuild: deb-pkg: avoid implicit effects

2019-03-17T03:56:23+00:00

* The man page for dpkg-source(1) notes:

>      -b, --build directory [format-specific-parameters]
>             Build  a  source  package  (--build since dpkg 1.17.14).
>             <...>
>
>             dpkg-source will build the source package with the first
>             format found in this ordered list: the format  indicated
>             with  the  --format  command  line  option,  the  format
>             indicated in debian/source/format, “1.0”.  The  fallback
>             to “1.0” is deprecated and will be removed at some point
>             in the future, you should always  document  the  desired
>             source   format  in  debian/source/format.  See  section
>             SOURCE PACKAGE FORMATS for an extensive  description  of
>             the various source package formats.

  Thus it would be more foolproof to explicitly use 1.0 (as we always
  did) than to rely on dpkg-source's defaults.

* In a similar vein, debian/rules is not made executable by mkdebian,
  and dpkg-source warns about that but still silently fixes the file.
  Let's be explicit once again.

Signed-off-by: Arseny Maslennikov 
Signed-off-by: Masahiro Yamada

kbuild: pkg: grep include/config/auto.conf instead of $KCONFIG_CONFIG

2019-03-13T17:39:13+00:00

This will be a little more efficient since unset CONFIG options are
stripped away from auto.conf, and we can hard-code the path to auto.conf
since it is never overridden.

include/config/kernel.release is generated before %pkg is run.
So, it is guaranteed auto.conf is up-to-date.

Signed-off-by: Masahiro Yamada

kbuild: deb-pkg: add CONFIG_ prefix to kernel config options

2019-03-13T17:39:12+00:00

This might be a kind of bike-shed, but I personally prefer grep'able
code.

I often do 'git grep CONFIG_FOO' instead of 'git grep FOO' when I
want to know where that CONFIG option is used.

This makes code longer, but I hope this is acceptable level.

Signed-off-by: Masahiro Yamada

deb-pkg: generate correct build dependencies

2019-03-13T17:30:26+00:00

bison/flex is now needed always for building for kconfig. Some build
dependencies depend on kernel configuration, enable them as needed:

- libelf-dev when UNWINDER_ORC is set
- libssl-dev for SYSTEM_TRUSTED_KEYRING

Since the libssl-dev is needed for extract_cert binary, denote with
:native to install the libssl-dev for the build machines architecture,
rather than for the architecture of the kernel being built.

Tested-by: Manivannan Sadhasivam 
Signed-off-by: Riku Voipio 
Reviewed-by: Ben Hutchings 
Acked-by: maximilian attems 
[masahiro.yamada: change 'flex' to 'flex | flex:native' ]
Signed-off-by: Masahiro Yamada

kbuild: pkg: use -f $(srctree)/Makefile to recurse to top Makefile

2019-02-20T00:42:46+00:00

'$(MAKE) KBUILD_SRC=' changes the working directory back and forth
between objtree and srctree.

It is better to recurse to the top-level Makefile directly.

Signed-off-by: Masahiro Yamada

kbuild: deb-pkg: fix too low build version number

2018-11-11T14:04:52+00:00

Since commit b41d920acff8 ("kbuild: deb-pkg: split generating packaging
and build"), the build version of the kernel contained in a deb package
is too low by 1.

Prior to the bad commit, the kernel was built first, then the number
in .version file was read out, and written into the debian control file.

Now, the debian control file is created before the kernel is actually
compiled, which is causing the version number mismatch.

Let the mkdebian script pass KBUILD_BUILD_VERSION=${revision} to require
the build system to use the specified version number.

Fixes: b41d920acff8 ("kbuild: deb-pkg: split generating packaging and build")
Reported-by: Doug Smythies 
Signed-off-by: Masahiro Yamada 
Tested-by: Doug Smythies

builddeb: Add automatic support for sh{3,4}{,eb} architectures

2018-07-28T01:53:44+00:00

Different generations of the SH architecture are not very compatible,
so there are/were separate Debian ports for SH3 and SH4.

Move the fallback out of the "case" statement, so that it will also be
used in case we find some SH architecture version without a known
mapping.

Signed-off-by: Ben Hutchings 
Signed-off-by: Masahiro Yamada

builddeb: Add automatic support for riscv* architectures

2018-07-28T01:53:44+00:00

Debian currently only defines "riscv64", but it seems safe to assume
that any 32-bit port will now be called "riscv32", also matching
$UTS_MACHINE.

Signed-off-by: Ben Hutchings 
Signed-off-by: Masahiro Yamada