| 1 Jun 2023 |
 trofi | If you do something like locally:
--- a/pkgs/development/tools/misc/libtool/libtool2.nix
+++ b/pkgs/development/tools/misc/libtool/libtool2.nix
@@ -53,0 +54 @@ stdenv.mkDerivation rec {
+ makeFlags = [ "-d" ];
you should be able to get libtool build logs with nix build -f. libtool.
| 06:34:51 |
| trofi | * If you do something like locally:
--- a/pkgs/development/tools/misc/libtool/libtool2.nix
+++ b/pkgs/development/tools/misc/libtool/libtool2.nix
@@ -53,0 +54 @@ stdenv.mkDerivation rec {
+ makeFlags = [ "-d" ];
you should be able to get libtool build logs with nix build -f. libtool.
| 06:35:11 |
 artemis | ty | 06:40:51 |
|  raphi changed their display name from raphi to raphi (element unread channel fix when). | 13:03:26 |
| artemis | trofi:
libtool-riscv64-unknown-linux-gnu> Prerequisite 'libtoolize.in' is newer than target 'doc/libtoolize.1'.
libtool-riscv64-unknown-linux-gnu> Must remake target 'doc/libtoolize.1'. | 21:32:34 |
| artemis | its not regenerating libtoolize.in though it seems like | 21:34:29 |
| artemis | libtool-riscv64-unknown-linux-gnu> Finished prerequisites of target file 'libtoolize.in'.
libtool-riscv64-unknown-linux-gnu> No need to remake target 'libtoolize.in'. | 21:34:30 |
| artemis | * its not regenerating libtoolize.in though it seems like. from earlier up the log: | 21:34:56 |
| trofi | Oh, it's a cross-compilation? | 21:34:58 |
| artemis | yeah | 21:35:04 |
| artemis | cross compiling from x86_64 to riscv64 | 21:35:41 |
| trofi | That I should be able to reproduce locally. Which package do you build? | 21:36:03 |
| trofi | (and I would expect libtoolize.in not to require a rebuild, what does log say, what triggers it's rebuild?) | 21:37:11 |
