Re: llama.cpp, whisper.cpp, ggml: Next steps

[Petter Reinholdtsen <pere@hungry.com>]

[Christian Kastner]
> Hm, that's odd for many reasons. For one, whisper-stream shouldn't need
> ggml, ldd is showing you libwhisper1's transitive dependency.

I know.

> Is libggml installed in the environment you tested this in? If not, that
> would explain the "not found".

Yes, it is installed, and ldd on libwhisper.so find it:

  % ldd debian/libwhisper1/usr/lib/x86_64-linux-gnu/libwhisper.so.1|grep ggml
        libggml.so => /usr/lib/x86_64-linux-gnu/ggml/libggml.so (0x00007fed76044000)
        libggml-base.so => /usr/lib/x86_64-linux-gnu/ggml/libggml-base.so (0x00007fed75f95000)
        libggml-cpu.so => /usr/lib/x86_64-linux-gnu/ggml/libggml-cpu.so (0x00007fed7594f000)
        libggml-hip.so => /usr/lib/x86_64-linux-gnu/ggml/libggml-hip.so (0x00007fed3f400000)
  %

> So (1) no ggml, but (2) RUNPATH *is* set (which we might actually not
> want for the binaries).

Same RUNPATH in the library:

  % objdump -x debian/libwhisper1/usr/lib/x86_64-linux-gnu/libwhisper.so.1 | grep -E '(NEEDED|RUNPATH)'
    NEEDED               libggml.so
    NEEDED               libggml-base.so
    NEEDED               libstdc++.so.6
    NEEDED               libm.so.6
    NEEDED               libgcc_s.so.1
    NEEDED               libc.so.6
    RUNPATH              /usr/lib/x86_64-linux-gnu/ggml
  %

> Oops, that was ambiguous. I meant: why DEB_TARGET_MULTIARCH instead of
> the more common DEB_HOST_MULTIARCH.

Ah.  I assume it is because the wanted value when cross-building is the
target arch, not the host arch.  I am not sure where I got the idea
from.

> I don't think I've encountered DEB_TARGET_ARCH before, so I may be
> overlooking something when using _HOST_.

I suspect mixing these two up will cause problems when cross-building
Debian packages.  Not a common problem, I believe.

-- 
Happy hacking
Petter Reinholdtsen