From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] File path name and bash pattern matching
Date: Sat, 18 Jun 2016 00:05:44 +0200 [thread overview]
Message-ID: <20160618000544.14d823af@gmx.net> (raw)
Hello,
some fun with a patch file name containing '?' and bash pattern matching, e.g:
$ make openssl-dirclean
Rename the original patch file substituting '?' with '_':
$ mv dl/openssl-1.0.2d-parallel-build.patch?id=c8abcbe8de5d3b6cdd68c162f398c011ff6e2d9d dl/openssl-1.0.2d-parallel-build.patch_id=c8abcbe8de5d3b6cdd68c162f398c011ff6e2d9d
Buildroot fails with misleading error message:
$ make
umask 0022 && make -C <some_path>/build O=<some_path>/build/.
openssl-1.0.2h.tar.gz: OK (sha256: 1d4007e53aad94a5b2002fe045ee7bb0b3d98f1a47f8b2bc851dcd1c74332919)
ERROR: No hash found for openssl-1.0.2d-parallel-build.patch_id=c8abcbe8de5d3b6cdd68c162f398c011ff6e2d9d
ERROR: No hash found for openssl-1.0.2d-parallel-build.patch_id=c8abcbe8de5d3b6cdd68c162f398c011ff6e2d9d
package/pkg-generic.mk:113: recipe for target '<some_path>/build/openssl-1.0.2h/.stamp_downloaded' failed
make[1]: *** [<some_path>/build/openssl-1.0.2h/.stamp_downloaded] Error 1
Makefile:16: recipe for target '_all' failed
make: *** [_all] Error 2
Removing the renamed patch file fixes the build:
$ rm dl/openssl-1.0.2d-parallel-build.patch_id=c8abcbe8de5d3b6cdd68c162f398c011ff6e2d9d
$ make
...starts with a fresh download of the missing patch file...
Which is the best way to avoid bash pattern matching here (in 'support/download/dl-wrapper')?
Regards,
Peter
reply other threads:[~2016-06-17 22:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160618000544.14d823af@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox