!FBuJyWXTGcGtHTPphC:nixos.org

Nix Rust

588 Members
Rust130 Servers

Load older messages


SenderMessageTime
28 Jun 2025
@dramforever:matrix.orgdramforever * we should probably do #399014 for rust. problem: how do we check for target is not x86-32? 07:33:10
@qyliss:fairydust.spaceAlyssa RossWe have a rustc wrapper07:40:33
@qyliss:fairydust.spaceAlyssa RossThat I think is to some extent already target-aware07:40:58
@dramforever:matrix.orgdramforeverso the problem afaiaw07:42:56
@dramforever:matrix.orgdramforeveris that cargo really wants to use the same rustc for building build.rs and proc macros as the one for building for target07:43:17
@dramforever:matrix.orgdramforeverso basically it's trying to use the same rustc as both (b, b, b) and (b, b, h)07:43:57
@qyliss:fairydust.spaceAlyssa RossThat's fine, isn't it?07:47:31
@qyliss:fairydust.spaceAlyssa RossThe wrapper can do different things depending on the target07:47:42
@dramforever:matrix.orgdramforever i don't think the wrapper as it is today knows about --target 07:48:57
@dramforever:matrix.orgdramforeverdo we somehow add parsing for it?07:49:02
@qyliss:fairydust.spaceAlyssa RossI thought it did08:00:43
@emilazy:matrix.orgemily
In reply to @dramforever:matrix.org
is that cargo really wants to use the same rustc for building build.rs and proc macros as the one for building for target
there's a specific cargo variable controlling some of this curse
08:26:23
@emilazy:matrix.orgemily or well 08:27:01
@emilazy:matrix.orgemilyjust see the note about targets in https://doc.rust-lang.org/cargo/reference/config.html#buildrustflags08:27:08
@emilazy:matrix.orgemilydunno if relevant to you or not, but a source of headaches for cross if one does not understand it08:27:22
@dramforever:matrix.orgdramforeveryeah doing it through cargo should be fine11:41:19
@dramforever:matrix.orgdramforeverthe idk two? packages using nixpkgs and compiling rust with just rustc can deal with it themselevs11:41:58
@dramforever:matrix.orgdramforever* the idk two? packages using nixpkgs and compiling rust with just rustc can deal with it themselves11:42:01
@dramforever:matrix.orgdramforeveralthough i wonder if it means we will have cargo and rustc with frame pointers enabled or not11:42:20
@emilazy:matrix.orgemily
In reply to @dramforever:matrix.org
we should probably do #399014 for rust. problem: how do we check for target is not x86(-32)?
oh I missed the context here. is it worth checking?
13:26:02
@emilazy:matrix.orgemilyour i686 support is entirely to run Steam and Wine13:26:11
@emilazy:matrix.orgemilyI'm not sure we have any Rust in there at all. maybe via Mesa?13:26:22
@dramforever:matrix.orgdramforever as fellow #exotic:nixos.org enjoyer i would rather not have to assume that 13:27:08
@dramforever:matrix.orgdramforever * as a fellow #exotic:nixos.org enjoyer i would rather not have to assume that 13:27:14
@dramforever:matrix.orgdramforeverfor anything, really13:27:27
@emilazy:matrix.orgemilyit doesn't actually break anything, right?13:27:59
@dramforever:matrix.orgdramforeverthe way that pr went with a kludge to carve out x86-32 is not ideal but at least i can say it's just dependent on targetPlatform13:28:01
@emilazy:matrix.orgemilyit's just slower13:28:02
@dramforever:matrix.orgdramforeveryes, it's just slower13:28:10
@emilazy:matrix.orgemilybeing able to pick our settings based on what's good for the platforms we actually support is part of why we have support tiers13:28:20

Show newer messages


Back to Room ListRoom Version: 6