| 25 Sep 2022 |
 piegames | But—why? | 19:30:15 |
 Artturin | nix-repl> builtins.baseNameOf bash
"p7bpdnxqd3i5hwm92mrscf7mvxk66404-bash-5.1-p16"
so it'll be embeded in the name
| 19:32:52 |
| Artturin | builtins.unsafeDiscardStringContext has to be used | 19:32:55 |
| Artturin | diff --git a/pkgs/build-support/trivial-builders/test-overriding.nix b/pkgs/build-support/trivial-builders/test-overriding.nix
index a16bbbee1b1..1ea8d7c0b90 100644
--- a/pkgs/build-support/trivial-builders/test-overriding.nix
+++ b/pkgs/build-support/trivial-builders/test-overriding.nix
@@ -91,7 +91,7 @@ let
# works at run time.
runTest = script:
let
- name = script.name or (builtins.baseNameOf script);
+ name = script.name or (builtins.unsafeDiscardStringContext (builtins.baseNameOf script));
in writeShellScript "run-${name}" ''
if [ "$(${script})" != "success" ]; then
echo "Failed in ${name}"
makes it pass too
| 19:33:37 |
| piegames | Artturin Thank you | 20:14:21 |
| 28 Sep 2022 |
|  coolshaurya changed their profile picture. | 17:32:55 |
| 3 Oct 2022 |
|  spacesbot - keeps a log of public NixOS channels joined the room. | 14:25:48 |
| Artturin | https://github.com/NixOS/nixpkgs/pull/194259 | 17:20:43 |
| 15 Oct 2022 |
|  underpantsgnome changed their display name from underpantsgnome to underpantsgnome!. | 00:34:19 |
| 17 Oct 2022 |
 hexa |
On x86_64 systems, x86_64 microarchitecture levels are mapped to additional system types (e.g. x86_64-v1-linux).
| 13:39:44 |
| hexa | John Ericson: nix since 2.4 supports building for given x86_64 abi levels, but nixpkgs doesn't allow that | 13:40:05 |
| hexa | ❯ 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 | ❯ 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 | * ❯ 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 | 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 | can you look into supporting that? | 13:41:29 |
| hexa | the rationale would be to flag certain packages with an abi level requirement, so build time does not get wasted | 13:43:19 |
| hexa | that applies mostly to the ML sector, where builds and tests are often quite costly | 13:43:36 |
| hexa | * ❯ 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 |
 sterni | 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 |
| sterni | When using autoconf it'll just be interpreted as a vendor and not do anything useful: | 19:56:23 |
| hexa | well, not sure what the point of having them in nix is 😄 | 19:56:26 |
| sterni | * 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 | saw the change and was wondering why we didn't support it in nixpkgs | 19:56:59 |
| sterni | I guess it saves you from having to create tags for these manually, but seems like a bad idea having malformed tuples in Nix proper | 19:59:58 |
| sterni | autoconf wants you to use feature macros: https://www.gnu.org/software/autoconf-archive/ax_check_x86_features.html | 20:00:11 |
| sterni | 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 |
| sterni | * 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 | gcc also uses -march= for it: https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=324bec558e95584e8c1997575ae9d75978af59f1 | 20:23:13 |
| sterni | https://github.com/NixOS/nix/pull/4551#issuecomment-1287905912 | 20:27:41 |
