Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#1445 - Unable to compile : "Cannot find appropriate hash command" #6409

Open
openwrt-bot opened this issue Mar 19, 2018 · 4 comments
Open

FS#1445 - Unable to compile : "Cannot find appropriate hash command" #6409

openwrt-bot opened this issue Mar 19, 2018 · 4 comments
Labels

Comments

@openwrt-bot
Copy link

@openwrt-bot openwrt-bot commented Mar 19, 2018

clauded1:

  • Device problem occurs on

TP-LINK Archer v2

  • Software versions of OpenWrt/LEDE release, packages, etc.

Trunk compiled under Ubuntu 18.04

  • Steps to reproduce

Trying to compile the latest trunk version of openwrt and I get the following error:

make[3]: Entering directory '/mnt/home/openwrt/trunk/toolchain/binutils'
mkdir -p /mnt/home/openwrt/trunk/dl
SHELL= flock /mnt/home/openwrt/trunk/tmp/.binutils-.tar.bz2.flock -c ' /mnt/home/openwrt/trunk/scripts/download.pl "/mnt/home/openwrt/trunk/dl" "binutils-.tar.bz2" "none" "" "@GNU/binutils/" '
Cannot find appropriate hash command, ensure the provided hash is either a MD5 or SHA256 checksum.
Makefile:118: recipe for target '/mnt/home/openwrt/trunk/dl/binutils-.tar.bz2' failed

Seems like "none" value should be "skip" instead. How do I fix that?

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Mar 19, 2018

jow-:

Looks like you use an outdated .config, referencing a removed binutils version. Note that the version number and tarball file name are not interpolated either in the download command line.

Does the issue persist after a "make defconfig" ?

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Mar 19, 2018

ffainelli:

This also happened to me. problem seems to be that if you have "Toolchain options" enabled, then you can run into that problem, since a previous binutils version was selected. I don't think we should be doing anything about that, since it clearly indicates that a previously used version is no longer supported, and the user picked one in particular, so we should now have that user select the next supported version that is appropriate.

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Mar 20, 2018

clauded1:

I had the "Toolchain options" selected and a binutils version specified...

Is there a way to specify "use latest supported binutils version" so I could automate my build process?

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Mar 31, 2018

Hauke:

Please run "make oldconfig" that should select a different binutils version and fix this problem.

Please report back if that solved your problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant