linux-toradex.git/scripts/package, branch v6.8-rc2

kbuild: deb-pkg: use debian/ for tmpdir

2024-01-10T11:39:47+00:00

Use debian/ for tmpdir, which is the default of debhelper.
This simplifies the code.

Signed-off-by: Masahiro Yamada 
Reviewed-by: Nicolas Schier

kbuild: deb-pkg: move 'make headers' to build-arch

2024-01-10T11:39:06+00:00

Strictly speaking, 'make headers' should be a part of build-arch
instead of binary-arch.

'make headers' constructs ready-to-copy UAPI headers in the kernel
directory.

Signed-off-by: Masahiro Yamada 
Reviewed-by: Nicolas Schier

kbuild: deb-pkg: do not search for 'scripts' directory under arch/

2024-01-05T10:35:38+00:00

The 'scripts' directory was searched under arch/${SRCARCH} to copy
arch/ia64/scripts, but commit cf8e8658100d ("arch: Remove Itanium
(IA-64) architecture") removed arch/ia64/ entirely.

There is another 'scripts' directory in arch/um/, but this script
is never executed with SRCARCH=um because UML does not support the
linux-headers package.

Signed-off-by: Masahiro Yamada

kbuild: deb-pkg: use build ID instead of debug link for dbg package

2024-01-05T10:35:38+00:00

There are two ways of managing separate debug info files:

 [1] The executable contains the .gnu_debuglink section, which specifies
     the name and the CRC of the separate debug info file.

 [2] The executable contains a build ID, and the corresponding debug info
     file is placed in the .build-id directory.

We could do both, but the former, which 'make deb-pkg' currently does,
results in complicated installation steps because we need to manually
strip the debug sections, create debug links, and re-sign the modules.
Besides, it is not working with module compression.

This commit abandons the approach [1], and instead opts for [2].

Debian kernel commit de26137e2a9f ("Drop not needed extra step to add
debug links") also stopped adding debug links.

Signed-off-by: Masahiro Yamada

kbuild: deb-pkg: use more debhelper commands in builddeb

2024-01-05T10:35:38+00:00

Commit 36862e14e316 ("kbuild: deb-pkg: use dh_listpackages to know
enabled packages") started to require the debhelper tool suite.

Use more dh_* commands in create_package():

 - dh_installdocs to install copyright
 - dh_installchangelogs to install changelog
 - dh_compress to compress changelog
 - dh_fixperms to replace the raw chmod command
 - dh_gencontrol to replace the raw dpkg-gencontrol command
 - dh_md5sums to record the md5sum of included files
 - dh_builddeb to replace the raw dpkg-deb command

Set DEB_RULES_REQUIRES_ROOT to 'no' in case debian/rules is executed
directly.

Signed-off-by: Masahiro Yamada 
Reviewed-by: Nicolas Schier

kbuild: deb-pkg: remove unneeded '-f $srctree/Makefile' in debian/rules

2024-01-05T10:35:38+00:00

This is unneeded because the Makefile in the output directory wraps
the top-level Makefile in the srctree.

Just run $(MAKE) irrespective of the build location.

Signed-off-by: Masahiro Yamada 
Reviewed-by: Nicolas Schier

kbuild: deb-pkg: allow to run debian/rules from output directory

2024-01-05T10:35:38+00:00

'make O=... deb-pkg' creates the debian directory in the output
directory. However, currently it is impossible to run debian/rules
created in the separate output directory.

This commit delays the $(srctree) expansion by escaping '$' and by
quoting the entire command, making it possible to run debian/rules in
the output directory.

Signed-off-by: Masahiro Yamada 
Reviewed-by: Nicolas Schier

kbuild: deb-pkg: set DEB_* variables if debian/rules is directly executed

2024-01-05T10:35:30+00:00

Since commit 491b146d4c13 ("kbuild: builddeb: Eliminate debian/arch
use"), direct execution of debian/rules results in the following error:

  dpkg-architecture: error: unknown option 'DEB_HOST_MULTIARCH'

The current code:

  dpkg-architecture -a$DEB_HOST_ARCH -qDEB_HOST_MULTIARCH

... does not look sensible because:

 - For this code to work correctly, DEB_HOST_ARCH must be pre-defined,
   which is true when the packages are built via dpkg-buildpackage.
   In this case, DEB_HOST_MULTIARCH is also likely defined, hence there
   is no need to query DEB_HOST_MULTIARCH in the first place.

 - If DEB_HOST_MULTIARCH is undefined, DEB_HOST_ARCH is likely undefined
   too. So, you cannot query DEB_HOST_MULTIARCH in this way. This is
   mostly the case where debian/rules is directly executed.

When debian/rules is directly executed, querying DEB_HOST_MUCHARCH is
not enough because we need to know DEB_{BUILD,HOST}_GNU_TYPE as well.

All DEB_* variables are defined when the package build is initiated by
dpkg-buildpackage, but otherwise, let's call dpkg-architecture to set
all DEB_* environment variables.

This requires dpkg 1.20.6 or newer because --print-format option
was added in dpkg commit 7c54fa2b232e ("dpkg-architecture: Add a
--print-format option").

Signed-off-by: Masahiro Yamada 
Reviewed-by: Nicolas Schier

kbuild: deb-pkg: squash scripts/package/deb-build-option to debian/rules

2023-12-29T13:25:21+00:00

The binary-arch target needs to use the same CROSS_COMPILE as used in
build-arch; otherwise, 'make run-command' may attempt to resync the
.config file.

Squash scripts/package/deb-build-option into debian/rules, as it is a
small amount of code.

Signed-off-by: Masahiro Yamada 
Reviewed-by: Nicolas Schier

kbuild: deb-pkg: factor out common Make options in debian/rules

2023-12-29T13:25:21+00:00

This avoids code duplication between binary-arch and built-arch.

Signed-off-by: Masahiro Yamada 
Reviewed-by: Nicolas Schier