!OqhvaDMJdKYUicLDiE:nixos.org

Nixpkgs Stdenv

229 Members
74 Servers

Load older messages


SenderMessageTime
28 Sep 2022
@coolshaurya:community.rscoolshaurya changed their profile picture.17:32:55
3 Oct 2022
@spacesbot:nixos.devspacesbot - keeps a log of public NixOS channels joined the room.14:25:48
@artturin:matrix.orgArtturinhttps://github.com/NixOS/nixpkgs/pull/19425917:20:43
15 Oct 2022
@tinybronca:sibnsk.netunderpantsgnome changed their display name from underpantsgnome to underpantsgnome!.00:34:19
17 Oct 2022
@hexa:lossy.networkhexa

On x86_64 systems, x86_64 microarchitecture levels are mapped to additional system types (e.g. x86_64-v1-linux).

13:39:44
@hexa:lossy.networkhexa John Ericson: nix since 2.4 supports building for given x86_64 abi levels, but nixpkgs doesn't allow that 13:40:05
@hexa:lossy.networkhexa
❯ nom-build -A hello --option system x86_64-v3-linux
error: Target specification with 3 components is ambiguous
⚠︎ Exited with 1 errors reported by nix at 15:38:23 after 0s
13:40:12
@hexa:lossy.networkhexa
❯ nix -vv --version
nix (Nix) 2.11.0
System type: x86_64-linux
Additional system types: i686-linux, x86_64-v1-linux, x86_64-v2-linux, x86_64-v3-linux
13:40:29
@hexa:lossy.networkhexa *
❯ nix -vv --version
nix (Nix) 2.11.0
System type: x86_64-linux
Additional system types: i686-linux, x86_64-v1-linux, x86_64-v2-linux, x86_64-v3-linux
[...]
13:40:35
@hexa:lossy.networkhexa

The error comes from here:

8c99aab lib/systems/parse.nix John Ericson         2017-02-09 16:09 -0500 442│       else throw "Target specification with 3 components is ambiguous";
13:41:02
@hexa:lossy.networkhexacan you look into supporting that?13:41:29
@hexa:lossy.networkhexathe rationale would be to flag certain packages with an abi level requirement, so build time does not get wasted13:43:19
@hexa:lossy.networkhexathat applies mostly to the ML sector, where builds and tests are often quite costly13:43:36
@hexa:lossy.networkhexa *
❯ nom-build -A hello --option system x86_64-v3-linux
error: Target specification with 3 components is ambiguous
⚠︎ Exited with 1 errors reported by nix at 15:38:23 after 0s

via https://github.com/NixOS/nix/pull/4551

13:44:04
22 Oct 2022
@sternenseemann:systemli.orgsterni hexa: FWIW x86_64-v1-linux etc. tuples are bogus, neither LLVM nor autotools accept those and it's quite understandable since they cause a huge nightmare when parsing 19:55:29
@sternenseemann:systemli.orgsterni When using autoconf it'll just be interpreted as a vendor and not do anything useful: 19:56:23
@hexa:lossy.networkhexawell, not sure what the point of having them in nix is 😄19:56:26
@sternenseemann:systemli.orgsterni *

When using autoconf it'll just be interpreted as a vendor and not do anything useful:

./result/config.sub x86_64-v2-linux
x86_64-v2-linux-gnu
19:56:30
@hexa:lossy.networkhexasaw the change and was wondering why we didn't support it in nixpkgs19:56:59
@sternenseemann:systemli.orgsterniI guess it saves you from having to create tags for these manually, but seems like a bad idea having malformed tuples in Nix proper19:59:58
@sternenseemann:systemli.orgsterniautoconf wants you to use feature macros: https://www.gnu.org/software/autoconf-archive/ax_check_x86_features.html20:00:11
@sternenseemann:systemli.orgsterni LLVM seems to rely on -march= for determining this (even though they have a “sub arch type” concept used for armv6 vs. armv7 for example, it is not used for this) 20:02:21
@sternenseemann:systemli.orgsterni * LLVM seems to rely on -march= for setting microarchitecture levels (even though they have a “sub arch type” concept used for armv6 vs. armv7 for example, it is not used for this) 20:02:31
@trofi:matrix.orgtrofigcc also uses -march= for it: https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=324bec558e95584e8c1997575ae9d75978af59f120:23:13
@sternenseemann:systemli.orgsternihttps://github.com/NixOS/nix/pull/4551#issuecomment-128790591220:27:41
31 Oct 2022
@tinybronca:sibnsk.netunderpantsgnome changed their display name from underpantsgnome! to underpantsgnome.20:20:18
1 Nov 2022
@emilytrau:matrix.orgemilytrau joined the room.21:44:42
6 Nov 2022
@artturin:matrix.orgArtturin why is there no overrideScope' in makeScopeWithSplicing 19:50:05
@artturin:matrix.orgArtturinis it simply not necessary?19:50:09
@artturin:matrix.orgArtturin John Ericson: 19:50:12

Show newer messages


Back to Room ListRoom Version: 9