[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#75237: Packaging ghostty terminal
From: |
Frank J. Cameron |
Subject: |
bug#75237: Packaging ghostty terminal |
Date: |
Fri, 10 Jan 2025 19:00:12 +0000 |
On Fri, Jan 10, 2025, at 3:26 PM, Frank J. Cameron wrote:
> starting phase `build'
> running: ("zig" "build" "--prefix" "" "--prefix-lib-dir" "lib"
> "--prefix-exe-dir" "bin" "--prefix-include-dir" "include" "--verbose"
> "-Dtarget=x86_64-linux-gnu" "-j2" "--release=fast")
> thread 1257 panic: unable to find module 'freetype'
> /gnu/store/ncxvllgf84qnnylw7b1snwvg2sapfc1g-zig-0.13.0/lib/zig/std/Build.zig:1857:18:
>
> 0x1152797 in module (build)
> panic("unable to find module '{s}'", .{name});
> ^
> /tmp/guix-build-ghostty-1.0.1.drv-0/source/build.zig:1114:67: 0x1152ce7
> in addDeps (build)
> step.root_module.addImport("freetype",
> freetype_dep.module("freetype"));
I think this is caused by unpack-dependencies; it's overwriting the top-level
dependency "freetype" (build.zig.zon -> pkg/freetype) with low-level dependency
"freetype" (pkg/freetype/build.zig.zon -> upstream source).
I'm not sure if rewriting rewriting the build.zig.zon files is better than
running in system mode with a populated pkgdir.