| 15 May 2025 |
 K900 | Are you on 24.11 or unstable? | 20:28:19 |
 staberinde | 24.11 | 20:29:15 |
| K900 | The file is definitely there for me on unstable | 20:29:29 |
| K900 | I have not checked 24.11 | 20:29:33 |
| staberinde | which file is that, fuse3.pc? | 20:31:20 |
| K900 | Yes | 20:32:35 |
| staberinde | I can confirm it's there in my 24.11 rev too /nix/store/c53z0p2yw9q2dfkxkvlpbz29g8n5isdc-fuse-3.16.2-dev/lib/pkgconfig/fuse3.pc | 20:57:59 |
| staberinde | but the odd thing is that if I get the same error even with PKG_CONFIG_PATH pointing to the above:
[root@majortheobaldslapper:/tmp/nix-build-borgtui-fdcf13ba063a9e8516e5bc5f679af5504304819d.drv-3]# source build/env-vars
[root@majortheobaldslapper:/build/source]# PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags fuse3 fuse3 >= 3.0.0
Package fuse3 was not found in the pkg-config search path.
Perhaps you should add the directory containing `fuse3.pc'
to the PKG_CONFIG_PATH environment variable
No package 'fuse3' found
Package fuse3 was not found in the pkg-config search path.
Perhaps you should add the directory containing `fuse3.pc'
to the PKG_CONFIG_PATH environment variable
No package 'fuse3' found
Package 3.0.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `3.0.0.pc'
to the PKG_CONFIG_PATH environment variable
No package '3.0.0' found
[root@majortheobaldslapper:/build/source]# echo $PKG_CONFIG
$PKG_CONFIG $PKG_CONFIG_ALLOW_CROSS
[root@majortheobaldslapper:/build/source]# export PKG_CONFIG_PATH=/nix/store/c53z0p2yw9q2dfkxkvlpbz29g8n5isdc-fuse-3.16.2-dev/lib/pkgconfig/
[root@majortheobaldslapper:/build/source]# PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags fuse3 fuse3 >= 3.0.0
Package 3.0.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `3.0.0.pc'
to the PKG_CONFIG_PATH environment variable
No package '3.0.0' found
[root@majortheobaldslapper:/build/source]# echo $PKG_CONFIG_PATH/
/nix/store/c53z0p2yw9q2dfkxkvlpbz29g8n5isdc-fuse-3.16.2-dev/lib/pkgconfig//
[root@majortheobaldslapper:/build/source]# ls -la $PKG_CONFIG_PATH/
total 12
dr-xr-xr-x 2 root root 4096 Jan 1 1970 .
dr-xr-xr-x 3 root root 4096 Jan 1 1970 ..
-r--r--r-- 2 root root 328 Jan 1 1970 fuse3.pc
[root@majortheobaldslapper:/build/source]#
| 21:00:50 |
| staberinde | wait nm, I think that's a quoting issue | 21:02:15 |
| staberinde | yep, setting PKG_CONFIG_PATH would fix it as expected
[root@majortheobaldslapper:/build/source]# PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags fuse3 fuse3>=3.0.0
[root@majortheobaldslapper:/build/source]# echo $?
0
[root@majortheobaldslapper:/build/source]# unset PKG_CONFIG_PATH
[root@majortheobaldslapper:/build/source]# PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags fuse3 fuse3>=3.0.0
Package fuse3 was not found in the pkg-config search path.
Perhaps you should add the directory containing `fuse3.pc'
to the PKG_CONFIG_PATH environment variable
No package 'fuse3' found
Package fuse3 was not found in the pkg-config search path.
Perhaps you should add the directory containing `fuse3.pc'
to the PKG_CONFIG_PATH environment variable
No package 'fuse3' found
| 21:05:21 |
| K900 | In reply to @staberinde:matrix.org
Currently I have
borg-tui = pkgs.rustPlatform.buildRustPackage (finalAttrs: rec {
pname = "borgtui";
version = "fdcf13ba063a9e8516e5bc5f679af5504304819d";
src = pkgs.fetchFromGitHub {
owner = "dpbriggs";
repo = pname;
rev = version;
sha256 = "7UbwW53HTM4oTbDnNruwjtF0KrnhoiCYXWl0CbXfMSk=";
};
nativeBuildInputs = [
pkgs.pkg-config
];
bulldInputs = [
pkgs.fuse3
];
cargoHash = "sha256-7F87unpr3OoY9SFBS2iwKhk2khYKH5w5xaENHUwnqC0=";
});
Fuck this | 21:10:06 |
| K900 | You misspelled buildInputs | 21:10:12 |
| K900 | This is your entire problem | 21:10:18 |
| staberinde | oh FFS | 21:10:26 |
| staberinde | good spot | 21:11:04 |
| staberinde | told you it was a stuoid question... | 21:11:19 |
| staberinde | * told you it was likely to be a stupid question... | 21:31:36 |
| 17 May 2025 |
|  terrorjack set a profile picture. | 08:53:43 |
|  oddlama changed their display name from oddlama to Malte. | 20:12:45 |
|  NixOS Moderation Bot banned  Shahar "Dawn" Or (persistent time-wasting). | 23:30:23 |
| 18 May 2025 |
|  @sneid:matrix.org left the room. | 10:34:33 |
|  Makuru joined the room. | 11:10:30 |
| Makuru | Is it possible to make rust builds with cargo, reproducible?
So that I get the exact same binary? | 11:13:02 |
 Alyssa Ross | what are you finding not to be reproducible? | 11:13:28 |
| Makuru | I haven't tested it yet but are there compiler flags or whatever I need to make a nix build reproducible? | 11:14:16 |
| Alyssa Ross | Generally we aim for reproducibility by default, but can't guarantee it, so you'll have to test to make sure. | 11:14:46 |
| Makuru | Also, can I make my flake check the output? Should I make a post install hook? | 11:16:25 |
| K900 | What do you mean by "check the output"? | 11:17:02 |
| Makuru | In reply to @k900:0upti.me
What do you mean by "check the output"? I mean to test it with a checksum. | 11:18:38 |
| Makuru | So others know that the build worked. | 11:18:57 |
