!OqhvaDMJdKYUicLDiE:nixos.org

Nixpkgs Stdenv

260 Members
80 Servers

Load older messages


SenderMessageTime
3 Sep 2023
@kity:kity.wtfproblems joined the room.21:33:29
4 Sep 2023
@roberthensing:matrix.orgRobert Hensing (roberth) changed their display name from Robert Hensing (roberth) to roberth.15:27:30
@roberthensing:matrix.orgRobert Hensing (roberth) changed their display name from roberth to Robert Hensing (roberth).15:28:17
@kity:kity.wtfproblemsoh! this room exists!19:41:30
@kity:kity.wtfproblems i was talking in #exotic:nixos.org about wanting to explore "wasi-native" nixpkgs, where every build is cross compiled from wasm64-wasi to your native architecture. that way, it wouldn't matter what your host is or if you're compiling "natively" or "cross" and you would be able to use heterogenous architectures to do distributed builds 19:44:39
@kity:kity.wtfproblemsi think the first step of this is creating a stdenv for wasi, but i have no idea where to start with that19:44:58
@kity:kity.wtfproblems * i was talking in #exotic:nixos.org about wanting to explore "wasi-native" nixpkgs, where every build is cross compiled from wasm64-wasi to your native architecture (using boot.binfmt.emulatedSystems = [ "wasm64-wasi" ]). that way, it wouldn't matter what your host is or if you're compiling "natively" or "cross" and you would be able to use heterogenous architectures to do distributed builds 19:45:47
5 Sep 2023
@trofi:matrix.orgtrofi For linux there pkgs/stdenv/linux/ and make-bootstrap-tools.nix which builds a set of minimal binaries to start from. 02:40:49
@trofi:matrix.orgtrofi Alternatively you can coerce pkgs/stdenv/default.nix to boot from system's binaries (impure or native build): might want to float stagesNative above. 02:42:41
@andreas.schraegle:helsinki-systems.de@andreas.schraegle:helsinki-systems.de left the room.15:00:42
11 Sep 2023
@amigdal:matrix.mit.eduArthur joined the room.02:13:22
13 Sep 2023
@winterqt:nixos.devWinter (she/her)

Hi all, poking my head in to confirm some weird thing.

Is it expected that libclang, if added to a derivation's nativeBuildInputs (strictDeps = false at that), will more or less completely blow up the ability to use Clang? (e.g. not being able to find any libc headers like stdbool.h.)

22:07:11
@winterqt:nixos.devWinter (she/her)I can only repro with a specific CMake project, trying to figure out a way to reduce the issue.22:10:02
@winterqt:nixos.devWinter (she/her) The reason I ask here is because it doesn't happen with buildInputs. 22:10:29
@winterqt:nixos.devWinter (she/her) The first suspect of CMAKE_INCLUDE_PATH differences isn't the case, hm. 22:25:00
@artturin:matrix.orgArtturin
In reply to @winterqt:nixos.dev

Hi all, poking my head in to confirm some weird thing.

Is it expected that libclang, if added to a derivation's nativeBuildInputs (strictDeps = false at that), will more or less completely blow up the ability to use Clang? (e.g. not being able to find any libc headers like stdbool.h.)

Diff the dumped env vars
22:31:35
@artturin:matrix.orgArtturin* In reply to @winterqt:nixos.dev Hi all, poking my head in to confirm some weird thing. Is it expected that libclang, if added to a derivation's nativeBuildInputs (strictDeps = false at that), will more or less completely blow up the ability to use Clang? (e.g. not being able to find any libc headers like stdbool.h.) Diff the dumped env vars after the setup22:31:55
@winterqt:nixos.devWinter (she/her)
In reply to@artturin:matrix.org
Diff the dumped env vars
That's what I'm doing, and nothing is different (after sorting + de-duping) that I've seen.
22:31:56
@winterqt:nixos.devWinter (she/her)It's definitely CMake-specific, but I'm still trying to figure out how, none of the CMAKE_* env vars are different in a substantial way (unless order matters, which it shouldn't).22:32:39
@artturin:matrix.orgArtturinIs this just the normal package set and not a pkgsLLVM or so22:33:00
@winterqt:nixos.devWinter (she/her)It's pkgsLLVM bc Darwin :/22:34:58
@winterqt:nixos.devWinter (she/her)FWIW I don't need it to be in nBI, I'm just trying to figure out why it breaks.22:35:23
@winterqt:nixos.devWinter (she/her)(specifically because mkShell.packages won't work then)22:35:36
@artturin:matrix.orgArtturinSo build != host?22:35:41
@artturin:matrix.orgArtturin
In reply to @winterqt:nixos.dev
(specifically because mkShell.packages won't work then)
.packages is bad anyways and the correct dependency attributes should be used
22:36:50
@winterqt:nixos.devWinter (she/her)
In reply to @artturin:matrix.org
So build != host?
build == host, this is a darwin build in a darwin machine + no strictDeps
22:50:20
@artturin:matrix.orgArtturinSo it's not pkgsLLVM22:51:52
@winterqt:nixos.devWinter (she/her)ah, that's what you were getting at22:52:49
@winterqt:nixos.devWinter (she/her) correct, it's just import nixpkgs {} 22:53:06
@winterqt:nixos.devWinter (she/her)i'll diff the remaining cmake env vars, doubt it'll come up with anything though22:54:28

Show newer messages


Back to Room ListRoom Version: 9