Leonardo Mörlein b993b68b6c build: introduce $(MKHASH) ... Before this commit, it was assumed that mkhash is in the PATH. While this was fine for the normal build workflow, this led to some issues if make TOPDIR="$(pwd)" -C "$pkgdir" compile was called manually. In most of the cases, I just saw warnings like this: make: Entering directory '/home/.../package/gluon-status-page' bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found [...] While these were only warnings and the package still compiled sucessfully, I also observed that some package even fail to build because of this. After applying this commit, the variable $(MKHASH) is introduced. This variable points to $(STAGING_DIR_HOST)/bin/mkhash, which is always the correct path. Signed-off-by: Leonardo Mörlein <me@irrelefant.net>		2021-05-13 15:13:15 +02:00
..
files	kernel/modules: relocate teql hotplug from iproute2 to kmod-sched	2021-03-19 15:30:01 +01:00
modules	kernel: add kmod-leds-uleds	2021-05-12 10:47:23 +02:00
Makefile	build: introduce $(MKHASH)	2021-05-13 15:13:15 +02:00