| 19 May 2025 |
maralorn | * Which platform are you on? | 20:14:08 |
keypusher | Seems to work | 20:14:08 |
maralorn | does it end in something like <hash>-lf-regstry3-<version>-doc? | 20:15:11 |
maralorn | * does it end in something like <hash>-lf-registry3-<version>-doc? | 20:15:21 |
keypusher | x86-linux | 20:15:54 |
keypusher | output: /nix/store/j4s4pxm1wmdgd5s14xlbmkc57fcrha60-RegistryThree-0.1.2.0-doc | 20:16:24 |
maralorn | Looks good. | 20:16:37 |
maralorn | Can you maybe rerun the build e.g. with nix build --print-build-logs .#default.doc and have a look for the haddockPhase being mentioned in the logs? | 20:17:19 |
maralorn | * Can you maybe rerun the build e.g. with nix build --check --print-build-logs .#default.doc and have a look for the haddockPhase being mentioned in the logs? | 20:17:27 |
keypusher | Jumped into a shell and did "cabal haddock", which does produce a documentation | 20:17:40 |
maralorn | Huh, I guess you don’t even need to rerun it. | 20:17:42 |
maralorn | You can do something like nix log .#default.doc I think. | 20:18:00 |
keypusher | ok | 20:18:12 |
keypusher | unrecognized flag "--check" ? | 20:19:32 |
keypusher | When i rebuild (after chaning some haddock ) My logs show this
...
Running phase: haddockPhase
Running phase: installPhase
...
| 20:28:23 |
keypusher | My .cabal file contains 1 lib, 2 binaries and one test module. Not sure if that can complicate things? | 20:29:41 |
maralorn | Curious. | 22:08:20 |
maralorn | Oh | 22:10:05 |
keypusher | Yeah, i'm running out of ideas. | 22:09:21 |
maralorn | Maybe your package has the isExecutable flag set? | 22:10:48 |
keypusher | The very last two lines of the build has this
RegistryThree> checking for references to /build/ in /nix/store/sr5drpczdv8vypi7xwg91r6hx9hy5syi-RegistryThree-0.1.2.0-doc...
RegistryThree> patching script interpreter paths in /nix/store/sr5drpczdv8vypi7xwg91r6hx9hy5syi-RegistryThree-0.1.2.0-doc
...im wondering if that patching part does something?
| 22:10:25 |
maralorn | I am looking at pkgs/development/haskell-modules/generic-builder.nix which describes the derivation in question. | 22:11:54 |
maralorn | And apparently haddocks only get build when the package counts as a library. | 22:12:34 |
keypusher | Sadly no | 22:11:59 |
maralorn | Maybe callCabal2nix sets the "isExecutable" flag. | 22:12:59 |
maralorn | You can try fixing it with isLibrary = true in the override you worked in before. | 22:14:15 |
maralorn | That didn’t help? | 22:21:20 |
keypusher | ill try that | 22:14:53 |
maralorn | Nope, the problem is quite certainly that no docs are being generated in the haddockPhase. | 22:21:50 |
keypusher | Thanks for trying to help btw. Much appreciated | 22:16:32 |