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
..
base-files	build: introduce $(MKHASH)	2021-05-13 15:13:15 +02:00
boot	ramips: mt7621: Add support for ZyXEL NR7101	2021-05-09 09:15:44 +02:00
devel
firmware	ipq40xx: add support for MikroTik SXTsq 5 ac	2021-04-29 10:55:07 +02:00
kernel	build: introduce $(MKHASH)	2021-05-13 15:13:15 +02:00
libs	build: introduce $(MKHASH)	2021-05-13 15:13:15 +02:00
network	build: introduce $(MKHASH)	2021-05-13 15:13:15 +02:00
system	build: introduce $(MKHASH)	2021-05-13 15:13:15 +02:00
utils	build: introduce $(MKHASH)	2021-05-13 15:13:15 +02:00
Makefile	build: fix opkg install step for large package selection	2021-05-12 11:13:53 +02:00