2a821d862c
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>
Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>
|
||
|---|---|---|
| .. | ||
| bin | ||
| lzma-loader | ||
| common-buffalo.mk | ||
| common-mikrotik.mk | ||
| common-netgear.mk | ||
| common-tp-link.mk | ||
| common-yuncore.mk | ||
| generic-tp-link.mk | ||
| generic-ubnt.mk | ||
| generic.mk | ||
| Makefile | ||
| nand.mk | ||
| tiny-netgear.mk | ||
| tiny-tp-link.mk | ||
| tiny.mk | ||