[GH-ISSUE #1747] Install scripts always dismiss some build configurations. #1100

New issue

Closed

opened 2026-10-29 14:48:33 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-29 14:48:33 +00:00

Owner

Originally created by @watamario15 on GitHub (Dec 25, 2025).
Original GitHub issue: https://github.com/kvcache-ai/ktransformers/issues/1747

Originally assigned to: @KMSorSMS on GitHub.

Reminder

I have read the above rules and searched the existing issues.

System Info

kt-kernel 0.5.0

Reproduction

I'm using kt-kernel and seeing some install settings are not treated correctly.

In CMakeLists.txt, the build configuration is forcefully set to Release by set(CMAKE_BUILD_TYPE "Release") and making CPUINFER_BUILD_TYPE env var useless.
In install.sh, CPUINFER_PARALLEL is set to 8 by default. But setup.py already has an infrastructure to automatically set the core count (detect_parallel_jobs()) which never gets triggered.
In install.sh, CPUINFER_VERBOSE is defined, but it seems like it never gets referenced and always shows verbose build logs (pip install . -v).

Are these intended behavior?

Others

No response

Originally created by @watamario15 on GitHub (Dec 25, 2025). Original GitHub issue: https://github.com/kvcache-ai/ktransformers/issues/1747 Originally assigned to: @KMSorSMS on GitHub. ### Reminder - [x] I have read the above rules and searched the existing issues. ### System Info kt-kernel 0.5.0 ### Reproduction I'm using `kt-kernel` and seeing some install settings are not treated correctly. - In `CMakeLists.txt`, the build configuration is forcefully set to `Release` by `set(CMAKE_BUILD_TYPE "Release")` and making `CPUINFER_BUILD_TYPE` env var useless. - In `install.sh`, `CPUINFER_PARALLEL` is set to `8` by default. But `setup.py` already has an infrastructure to automatically set the core count (`detect_parallel_jobs()`) which never gets triggered. - In `install.sh`, `CPUINFER_VERBOSE` is defined, but it seems like it never gets referenced and always shows verbose build logs (`pip install . -v`). Are these intended behavior? ### Others _No response_

bsakaguchi

2026-10-29 14:48:33 +00:00

closed this issue
added the
bug
label

bsakaguchi commented

2026-10-29 14:48:33 +00:00

Author

Owner

@ErvinXie commented on GitHub (Dec 25, 2025):

These might be some mistakes. You can fix them for us if you are interested.

@ErvinXie commented on GitHub (Dec 25, 2025): These might be some mistakes. You can fix them for us if you are interested.

bsakaguchi commented

2026-10-29 14:48:34 +00:00

Author

Owner

@watamario15 commented on GitHub (Jan 12, 2026):

Hey, sorry for being late but I made a quick fix at #1789. Could you check if this PR aligns with your intention and the project standard?

@watamario15 commented on GitHub (Jan 12, 2026): Hey, sorry for being late but I made a quick fix at #1789. Could you check if this PR aligns with your intention and the project standard?

bsakaguchi referenced this issue

2026-10-29 14:53:29 +00:00

[PR #1100] [MERGED] Update llama4.md #1560