| 1 Jun 2023 |
 trofi | (and I would expect libtoolize.in not to require a rebuild, what does log say, what triggers it's rebuild?) | 21:37:11 |
 artemis | vi@philomena ~/z/nixpkgs (nixos-22.11)> nix build -f. pkgsCross.riscv64.libtool | 21:37:14 |
| artemis | commit 9af373a61647257d16ae6062cddaa9094d24920c to be exact | 21:37:24 |
| trofi | nod, i'll try on staging-next first | 21:37:38 |
| artemis | In reply to @trofi:matrix.org
(and I would expect libtoolize.in not to require a rebuild, what does log say, what triggers it's rebuild?) nothing, it doesnt rebuild | 21:37:43 |
| artemis | look up there it says no need to remake target libtoolize.in | 21:37:53 |
| artemis | so libtoolize.in is not rebuilt. but it is newer than doc/libtoolize.1 which does rebuild | 21:38:21 |
| trofi | Aha. Then some other prerequisite is stale if it still wants to rebuild doc/libtoolize.1. Maybe a few lines earlier. | 21:38:39 |
| artemis | hmm? no it says that libtoolize.in is newer | 21:39:01 |
| artemis | and is the reason for the rebuild | 21:39:09 |
| artemis | here is the full evaluation of libtoolize.1 https://dpaste.com/G93P2BJ5X | 21:40:51 |
| trofi | Hm. If you add --keep-failed you can check both files' timestamps in temp dir. I wonder if one of them matches build time. | 21:41:53 |
