allow sha1 hash checking command to be configured

This commit is contained in:
Peter Jin 2020-03-06 23:12:57 -05:00 committed by Rich Felker
parent a54eb56f33
commit 5086175f29
2 changed files with 10 additions and 2 deletions

View File

@ -25,6 +25,7 @@ LINUX_SITE = https://cdn.kernel.org/pub/linux/kernel
LINUX_HEADERS_SITE = http://ftp.barfooze.de/pub/sabotage/tarballs/ LINUX_HEADERS_SITE = http://ftp.barfooze.de/pub/sabotage/tarballs/
DL_CMD = wget -c -O DL_CMD = wget -c -O
SHA1_CMD = sha1sum -c
COWPATCH = $(CURDIR)/cowpatch.sh COWPATCH = $(CURDIR)/cowpatch.sh
@ -76,7 +77,7 @@ $(SOURCES)/config.sub: | $(SOURCES)
mkdir -p $@.tmp mkdir -p $@.tmp
cd $@.tmp && $(DL_CMD) $(notdir $@) "http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=$(CONFIG_SUB_REV)" cd $@.tmp && $(DL_CMD) $(notdir $@) "http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=$(CONFIG_SUB_REV)"
cd $@.tmp && touch $(notdir $@) cd $@.tmp && touch $(notdir $@)
cd $@.tmp && sha1sum -c $(CURDIR)/hashes/$(notdir $@).$(CONFIG_SUB_REV).sha1 cd $@.tmp && $(SHA1_CMD) $(CURDIR)/hashes/$(notdir $@).$(CONFIG_SUB_REV).sha1
mv $@.tmp/$(notdir $@) $@ mv $@.tmp/$(notdir $@) $@
rm -rf $@.tmp rm -rf $@.tmp
@ -84,7 +85,7 @@ $(SOURCES)/%: hashes/%.sha1 | $(SOURCES)
mkdir -p $@.tmp mkdir -p $@.tmp
cd $@.tmp && $(DL_CMD) $(notdir $@) $(SITE)/$(notdir $@) cd $@.tmp && $(DL_CMD) $(notdir $@) $(SITE)/$(notdir $@)
cd $@.tmp && touch $(notdir $@) cd $@.tmp && touch $(notdir $@)
cd $@.tmp && sha1sum -c $(CURDIR)/hashes/$(notdir $@).sha1 cd $@.tmp && $(SHA1_CMD) $(CURDIR)/hashes/$(notdir $@).sha1
mv $@.tmp/$(notdir $@) $@ mv $@.tmp/$(notdir $@) $@
rm -rf $@.tmp rm -rf $@.tmp

View File

@ -46,6 +46,13 @@
# DL_CMD = wget -c -O # DL_CMD = wget -c -O
# DL_CMD = curl -C - -L -o # DL_CMD = curl -C - -L -o
# Check sha-1 hashes of downloaded source archives. On gnu systems this is
# usually done with sha1sum.
# SHA1_CMD = sha1sum -c
# SHA1_CMD = sha1 -c
# SHA1_CMD = shasum -a 1 -c
# Something like the following can be used to produce a static-linked # Something like the following can be used to produce a static-linked
# toolchain that's deployable to any system with matching arch, using # toolchain that's deployable to any system with matching arch, using
# an existing musl-targeted cross compiler. This only works if the # an existing musl-targeted cross compiler. This only works if the