Ticket Change Details
Overview

Artifact ID: bfdb8b15c9d56b07a95c9cc565c30dfe27598a6913d9d88db19746855f69c1d1
Ticket: c0cd214ad4722efae9bf669c7db4abcfa93d4473
Building And Testing Against A Static OpenSSL Fails
User & Date: bohagan on 2026-10-12 17:11:44
Changes

  1. icomment:
    Just to be clear, you are trying to create a static TclTLS library using a static OpenSSL library, then load that into TCL? If so, you have the right compile options to create the library, assuming the OpenSSL libcrypto.a and libssl.a files are available in the paths you specified. Most Linux distributions don't include them anymore.
    
    The failed make-docs-n is likely due to you having a ~name or HOME env var in your path. TCL 9.0 doesn't support tilde paths anymore. Please check that and let me know. The right workaround is to do a 'make binaries'.
    
    The pkgIndex.tcl file is only installed for shared libraries. This is inherited from the sample extension makefile. Likely this is because we don't know where to put it for static builds. I can fix this, but...
    
    However, the load will fail since you can't load static libraries, you need to link them to tcl when you compile tcl. The package require then needs to load an empty library like on TCL 8.6. So, I can fix that. However the real issue is you need to call the library from your app. You need something like https://core.tcl-lang.org/tcl/file?name=unix/tclAppInit.c to make it work.
    
    There are a few TCL distributions that statically compile extensions. They may be a good source of information on how to make it work.
    
  2. login: "bohagan"
  3. mimetype: "text/plain"
  4. priority changed to: "Immediate"
  5. resolution changed to: "Open"