indygreg / indygreg/PyOxidizer

Unable to Use libopenSSL in compiled application

Open
#757 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
6.2k
Forks
256
PR merge metrics
No merged PRs in 30d

Description

Hi!

I'm very excited to transition my python app from nuitka to a rust-first binary with signing etc. I've got *almost* everything working. Here's my `pyoxidizer.bzl` file: (as a `.txt`, because github)

[pyoxidizer.txt](https://github.com/user-attachments/files/18050567/pyoxidizer.txt)

The goal of this particular project is simple: Shut up, be a binary, load the python code that does the real work.
This *almost* works perfectly, but I can't quite tell why `pyoxidizer` is missing the libopenssl library `curldl` is after, here.
Runtime logs follow:
```
18:51:37 sk3shun-8@UNDEAD-ASYLUM GitHub/umomwd ? 1 % ./src-rs/build/x86_64-unknown-linux-gnu/debug/install/umo-rs info
Traceback (most recent call last):
File "runpy", line 196, in _run_module_as_main
File "runpy", line 86, in _run_code
File "umo", line 554, in
File "umo", line 206, in
File "umo", line 179, in call_subcmd
File "subcmds", line 35, in
File "handlers", line 27, in
File "curldl", line 3, in
File "curldl.curldl", line 12, in
ImportError: libssl-52849bc7.so.1.1.1k: cannot open shared object file: No such file or directory
```

Just to be clear, I've got `libssl-1.1` all over my system in tons of locations. But not under this specific name. So it seems clear to me that pyoxidizer is linking against something I've not actually provided in my config... I'm just not sure how to tell it to link against that!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the attached pyoxidizer.bzl configuration and reproduce the packaged binary command shown in the traceback. Trace how curldl requests libssl-52849bc7.so.1.1.1k and how PyOxidizer handles that dependency; done means the compiled application runs without the missing-library ImportError.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.