Kay Hayen

Would you have the compilation report for upload, or the snippet that indicates why it's included (or if not)?

So, the one line that is relevant is this right here: > So, it seems this is indeed included by Nuitka, and then after modifying it with `patchelf` for use...

I need to check what my commercial containers and CentOS containers in general use, but I guess/hope it's not that version.

For Nuitka is probably means that we should error check the patchelf version. I am also kind of annoyed by the fact that the tools versions used are not recorded...

Finally took the time, for this to be checked, now patchelf 0.18.0 precisely is rejected at compilation start. This will be in the 2.3 release and is coming to the...

Oh, that's still interesting news to me, I wasn't aware of that.

Nuitka should know this ahead of time, and maybe this is about it using a Windows resource for the onefile attached data, and wouldn't happen with payload attached in the...

So, resources have a 2GB limit, and the PE file spec says that there is a 2GB limit for the image size, so we are kind of lost there more...

Pick up the `torch\include` files seems very wasteful, I wonder if it can do without. Compiling on the target machine is very unlikely to be done on at least Windows....

The help output of Nuitka for data files will be your friend when it comes to data files. The one for modules, not.