Skip to content

Misc. bug: default.metallib can't be found when it is placed near the binary with different execution dir, symlink can't be resolved. #10675

@ormandi

Description

@ormandi

Name and Version

$ llama-cli --version
register_backend: registered backend Metal (1 devices)
register_device: registered device Metal (AMD Radeon Pro 5500M)
register_backend: registered backend BLAS (1 devices)
register_device: registered device BLAS (Accelerate)
register_backend: registered backend CPU (1 devices)
register_device: registered device CPU (Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz)
version: 4256 (ad5734c)
built with Apple clang version 16.0.0 (clang-1600.0.26.4) for x86_64-apple-darwin23.6.0

Operating systems

Mac

Which llama.cpp modules do you know to be affected?

libllama (core library)

Problem description & steps to reproduce

Move default.metallib out of the execution directory e.g. near the binary or make it a symlink.

First Bad Commit

No response

Relevant log output

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions