Leonardo Mörlein 49fde42a9c 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>
Signed-off-by: maurerr <mariusd84@gmail.com>
2021-09-01 08:08:05 +00:00
..
2021-09-01 08:07:35 +00:00
2020-02-22 16:34:57 +01:00
2021-09-01 08:07:55 +00:00
2021-09-01 08:07:35 +00:00
2019-01-24 10:39:30 +01:00
2021-09-01 08:07:35 +00:00
2019-11-01 21:19:40 +01:00
2021-09-01 08:07:43 +00:00
2021-09-01 08:07:47 +00:00
2021-09-01 08:07:44 +00:00
2021-09-01 08:07:44 +00:00
2021-09-01 08:07:49 +00:00
2021-09-01 08:07:22 +00:00
2021-09-01 08:08:05 +00:00
2021-09-01 08:07:40 +00:00
2019-02-26 23:20:04 +01:00
2021-09-01 08:07:35 +00:00
2021-09-01 08:07:40 +00:00
2021-09-01 08:07:41 +00:00