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
..
lzma-loader
common-tp-link.mk
Makefile	build: introduce $(MKHASH)	2021-05-13 15:13:15 +02:00
mt76x8.mk	treewide: make AddDepends/usb-serial selective	2021-03-06 12:38:38 +01:00
mt7620.mk	build: introduce $(MKHASH)	2021-05-13 15:13:15 +02:00
mt7621.mk	build: introduce $(MKHASH)	2021-05-13 15:13:15 +02:00
rt288x.mk
rt305x.mk	ramips: rt305x: use lzma-loader for ZyXEL Keenetic Lite rev.B	2021-04-08 09:20:59 +02:00
rt3883.mk