!FBuJyWXTGcGtHTPphC:nixos.org

Nix Rust

647 Members
Rust152 Servers

Load older messages


SenderMessageTime
20 Oct 2025
@anders:sorby.xyzAndersI get the same macro errors as in 1.89.0 12:43:17
@let_rec:floss.uzrec joined the room.13:07:07
@vlmutolo:matrix.org@vlmutolo:matrix.org left the room.15:55:08
@anders:sorby.xyzAndersOk, they are still using nightly features. But we can still use my nix build using rust nightly.16:02:40
@k900:0upti.meK900No16:03:31
@k900:0upti.meK900We can't16:03:32
@k900:0upti.meK900We will not allow Rust nightlies in nixpkgs, as that's a maintenance nightmare long term16:03:46
@anders:sorby.xyzAnders I mean just to compile it outside nixpkgs. It is a flake. 16:05:29
@anders:sorby.xyzAndershttps://github.com/Anderssorby/relibc/blob/add-nix-build/flake.nix16:06:18
@k900:0upti.meK900Outside of nixpkgs you can do whatever you want yeah16:10:13
@hexa:lossy.networkhexa curious case of cargo metadata call of a libraries build.rs erroring out due to a missing optional dependency (libz-rs-sys) when libz-sys has been chosen instead by the lockfile of the application 20:01:24
@hexa:lossy.networkhexaugh, I'm rewriting that20:01:49
@hexa:lossy.networkhexa * I have a curious case where a library's build.rs calls cargo metadata and fails because an optional dependency (libz-rs-sys) is missing. 20:02:41
@hexa:lossy.networkhexa * Servo has locked libz-sys instead, which is an alternative to libz-rs-sys and that has been correctly vendored. 20:03:02
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/45395720:03:22
@hexa:lossy.networkhexa
called `Result::unwrap()` on an `Err` value: CargoMetadata { 
  stderr: "error: no matching package found\nsearched package name: `libz-rs-sys`
  perhaps you meant:      libdbus-sys or libz-sys
  location searched: directory source `/build/servo-0.0.1-unstable-2025-10-20-vendor` (which is replacing registry `crates-io`)
  required by package `mozjs_sys v0.140.0-6 (/build/servo-0.0.1-unstable-2025-10-20-vendor/mozjs_sys-0.140.0-6)`
" }
20:03:32
@hexa:lossy.networkhexareproducer included, but I'm frankly lost again20:03:58
@hexa:lossy.networkhexa
  preBuild = ''
    pushd ../servo-*-vendor/mozjs*sys*/
    cargo metadata
    exit 1
  '';
20:04:09
@hexa:lossy.networkhexa *
  preBuild = ''
    pushd ../servo-*-vendor/mozjs*sys*/
    cargo metadata
    exit 1
  '';
20:04:11
@albertlarsan68:albertlarsan.frAlbert Larsan There exists the FORBIDDEN internal-only RUSTC_BOOTSTRAP=1 env var IIRC if you want to use nightly features on stable, but you shouldn't. 20:41:25
21 Oct 2025
@dramforever:matrix.orgdramforever don't grep RUSTC_BOOTSTRAP in nixpkgs 04:43:27
@andrewzah:matrix.abare.partyAndrew Zah set a profile picture.09:49:41
@sandro:supersandro.deSandro 🐧A friendly reminder about https://github.com/NixOS/nixpkgs/pull/45117914:38:56
@niklaskorz:matrix.orgniklaskorztested two meson-based packages and they build fine22:04:06
@niklaskorz:matrix.orgniklaskorzso from my perspective there have been enough reference packages in the comments that show this is good to go as-is22:07:08
@sandro:supersandro.deSandro 🐧nice, thank you22:41:13
@niklaskorz:matrix.orgniklaskorz let's give Alyssa Ross same more time to react but otherwise I'd merge it tomorrow 23:03:49
@niklaskorz:matrix.orgniklaskorz
In reply to @hexa:lossy.network
ugh, I'm rewriting that
After going through the relevant Cargo.tomls in servo and mozjs I can only conclude that this is the correct behavior
23:17:46
@niklaskorz:matrix.orgniklaskorz I don't have an answer yet why cargo metadata would try to fetch a dependency that's disabled by default though 23:18:10
@hexa:lossy.networkhexa there is --locked for cargo metadata, but mozjs doesn't lock anything 23:20:26

Show newer messages


Back to Room ListRoom Version: 6