Hello Roy,<div><br /></div><div>I download the latest Kit-creator package to try building one for my RHEL5 x86_64 machine. I am facing a fatal stop issue while downloading the tcl package. Here is the log printed by kitcreator on shell</div><div>=============================</div><div><div>~396$ ./kitcreator --enable-64bit</div><div>Building tcl ... &nbsp;Unable to download source code for Tcl.</div><div>&nbsp; Aborting Tcl -- further packages will likely also fail.</div><div>&nbsp;failed.</div><div>./kitcreator: line 297: /tclConfig.sh: No such file or directory</div></div><div>=============================</div><div><br /></div><div>If I check inside the tcl/build.log then</div><div>---------------------------------------------------</div><div><div>2017-09-08 14:05:29 (551 KB/s) - `src/tcl8.6.7.tar.gz.new' saved [9687799/9687799]</div><div><br /></div><div>unknown option '-sha256'</div><div>options are</div><div>-c &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;to output the digest with separating colons</div><div>-d &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;to output debug info</div><div>-hex &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;output as hex dump</div><div>-binary &nbsp; &nbsp; &nbsp; &nbsp; output in binary form</div><div>-sign &nbsp; file &nbsp; &nbsp;sign digest using private key in file</div><div>-verify file &nbsp; &nbsp;verify a signature using public key in file</div><div>-prverify file &nbsp;verify a signature using private key in file</div><div>-keyform arg &nbsp; &nbsp;key file format (PEM or ENGINE)</div><div>-signature file signature to verify</div><div>-binary &nbsp; &nbsp; &nbsp; &nbsp; output in binary form</div><div>-engine e &nbsp; &nbsp; &nbsp; use engine e, possibly a hardware device.</div><div>-md5 to use the md5 message digest algorithm (default)</div><div>-md4 to use the md4 message digest algorithm</div><div>-md2 to use the md2 message digest algorithm</div><div>-sha1 to use the sha1 message digest algorithm</div><div>-sha to use the sha message digest algorithm</div><div>-mdc2 to use the mdc2 message digest algorithm</div><div>-ripemd160 to use the ripemd160 message digest algorithm</div><div>Hash (sha256) mismatch: Got: ; Expected: 7c6b8f84e37332423cfe5bae503440d88450da8cc1243496249faa5268026ba5</div></div><div>-------------------------------------------------</div><div><br /></div><div>I am unable to trace which command is resulting in this fatal issue. Kindly help resolve this problem at the earliest.</div><div><br /></div><div>Thanks,</div><div>Madhur</div>