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

[Christian Kastner <ckk@debian.org>]

On 2025-02-26 21:29, Petter Reinholdtsen wrote:
> I forgot to mention I had to adjust the ggml build slightly, to include
> the ggml-cpp.h file.  Patch sent upstream as
> <URL: https://github.com/ggml-org/ggml/pull/1126 >.

Indeed, I hit that with llama as well.

> Note, to get the programs in the whisper.cpp package working, one need
> to se LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/ggml/ or similar.  I
> have not been able to get cmake to install a rpath/runpath into the
> binaries.

I was going to look at this, but pristine-tar is having troubles with 1.7.4:

> # pristine-tar checkout whisper.cpp_1.7.4.orig.tar.gz
> xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
> xdelta3: normally this indicates that the source file is incorrect
> xdelta3: please verify the source file with sha1sum or equivalent
> xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
> xdelta3: normally this indicates that the source file is incorrect
> xdelta3: please verify the source file with sha1sum or equivalent
> xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
> xdelta3: normally this indicates that the source file is incorrect
> xdelta3: please verify the source file with sha1sum or equivalent
> xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
> xdelta3: normally this indicates that the source file is incorrect
> xdelta3: please verify the source file with sha1sum or equivalent
> xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
> xdelta3: normally this indicates that the source file is incorrect
> xdelta3: please verify the source file with sha1sum or equivalent
> xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
> xdelta3: normally this indicates that the source file is incorrect
> xdelta3: please verify the source file with sha1sum or equivalent
> pristine-tar: Failed to reproduce original tarball. Please file a bug report.
> pristine-tar: failed to generate tarball

1.7.3 still works fine.

Tested on bookworm, and unstable.

As I don't have the original tarball, could you report the bug?

#924912 might be related, though I think this is one of the "old"
problems with pristine-tar: tar changes, and the archive is no longer
reproducible. Or some such.

Best,
Christian