Overview
Artifact ID: | 34fd3b5d6e43d121051ba9c003e2e84a5cfd7bfc6bb9ce70f2f1aaa45760a568 |
---|---|
Ticket: | 8f0ff730836505e298defe424329cd0fb9527efc
tcllibc and sha256c leads to error "Headers for API sha256c not found in" |
User & Date: | aku 2024-09-17 14:17:18 |
Changes
- icomment:
Ah. The `package require tcllibc` loads the tcllibc shlib, and that runs a `package provide sha256c` internally, so the `require sha256c` short-circuits, i.e. becomes a nop. Is your situation the ahead-of-time compilation of a package using sha256c ? Or is it using critcl/sha256c in compile-at-runtime mode ? From the description it looks it feels to be latter. However it may simply be the reduction of your larger test case. You could try to put a `package forget sha256c` just before the `package require sha256c`. That should be a nop if neither sha256c nor tcllibc are loaded. However, when a tcllibc was loaded before, then the forget should cancel the `provide sha256` tcllibc made, forcing critcl into the execution of sha256c.tcl.
- login: "aku"
- mimetype: "text/x-markdown"