Nixpkgs Stdenv - Public Room Timeline

	Nixpkgs Stdenv	266 Members
		82 Servers

Load older messages

Sender	Message	Time
1 Oct 2023
Artturin	* asking because https://github.com/NixOS/nixpkgs/pull/258476	20:56:01
Artturin	Cleaning up the bootstrap to make automating the updating of the bootstrap files easier	20:56:46
Weijia	There was an effort to bootstrap a loongarch64-linux native stdenv a few months ago	21:05:46
Weijia	I assume the interest was lost after #238154, see #252590.	21:05:49
2 Oct 2023
trofi	Yeah, I personally had to give up on nixpkgs for cross-compiler infra.	06:43:26
Artturin	https://github.com/NixOS/nixpkgs/pull/258540	07:18:00
Artturin	Preliminary work, I don't yet have a updater script but I think having the job names match the bootstrap file names will make the updater script more straightforward and have less special-cases	07:23:26
Artturin	* Preliminary work, I don't yet have a updater script but I think having the job names match the bootstrap filenames will make the updater script more straightforward and have less special-cases	07:23:51
4 Oct 2023
trofi	`__FILE__` mangling is still up for review: https://github.com/NixOS/nixpkgs/pull/255192 . I did not see any regressions for the past week of trying to use it.	05:17:50
8 Oct 2023
Artturin	In reply to @trofi:matrix.org `__FILE__` mangling is still up for review: https://github.com/NixOS/nixpkgs/pull/255192 . I did not see any regressions for the past week of trying to use it. merged	01:32:04
11 Oct 2023
	Rhys joined the room.	02:25:33
vcunat	Hello, any hint how to avoid autotools dependencies when I need to patch `./configure`? I created patch for `configure` along with the one for `configure.ac`. Configure phase is OK, but when build phase starts, it wants `aclocal` and I can't see why.	08:33:40
Artturin	In reply to @vcunat:matrix.org Hello, any hint how to avoid autotools dependencies when I need to patch `./configure`? I created patch for `configure` along with the one for `configure.ac`. Configure phase is OK, but when build phase starts, it wants `aclocal` and I can't see why. I don't know what they use to detect changes but maybe just try `touch`ing both files?	09:03:23
Artturin	In reply to @vcunat:matrix.org Hello, any hint how to avoid autotools dependencies when I need to patch `./configure`? I created patch for `configure` along with the one for `configure.ac`. Configure phase is OK, but when build phase starts, it wants `aclocal` and I can't see why. * I don't know what they use to detect changes but maybe just try `touch`ing both files in postPatch?	09:03:36
vcunat	I did try that.	09:03:43
vcunat	But in the meantime I found that more of `Makefile.in` patching is needed than I was doing. (I just applied the same as `Makefile.am` but that does not suffice.)	09:04:27
vcunat	I suppose I'll just try doing autoreconf locally and hardcode the whole diff into nixpkgs patch :-( Hopefully that ugly thing will work.	09:05:13
Artturin	ah i assumed you already did that	09:05:48
vcunat	Patches that add .c and .h files are harder than I expected.	09:05:58
vcunat	Uh, it generates huge diffs of unrelated changes. Matching versions of all autotools with upstream is probably hard.	09:08:52
Artturin	try touching `aclocal.m4`	09:09:09
Artturin	https://stackoverflow.com/questions/33278928/how-to-overcome-aclocal-1-15-is-missing-on-your-system-warning	09:09:14
Artturin	vcunat:	09:10:21
Artturin	or touching all 3	09:11:06
vcunat	Thanks! Touching that file does resolve this issue. I'll most likely use it - I hope I'll manage to finish the whole hacky patching.	09:19:51
vcunat	Uh, I made some mistake. I don't think it succeeded. I probably omitted the patch by mistake.	09:54:30
vcunat	I don't know, I'll probably give it up for the current staging-next-23.05. In case someone wants to experiment, you can get prototype patch for nghttp2 (version without touching generated stuff): https://github.com/vcunat/nghttp2/pull/new/p/backport-cve-2023-44487	10:20:33
14 Oct 2023
p14	I've just discovered (messing around on staging) that a `nix shell .#pkgsLLVM.buildPackages.stdenv.cc` gives you a `x86_64-unknown-linux-clang` can't compile things. The linker fails, unable to find libunwind and friends. The reason is that the logic for adding the appropriate `-L` flags is actually handled by the bintools setuphook. The packages are named as extraPackages in the clang wrapper: https://github.com/NixOS/nixpkgs/blob/176015fc743583e30581c23bfda2bf848dd4d67d/pkgs/development/compilers/llvm/16/default.nix#L247-L252 This results in NIX_LDFLAGS having a `-L/path/to/libunwind` (and libcxx, etc), if you're in a stdenv, and not otherwise. My conclusion is that the compiler only works if you're in a stdenv, but I feel that it should work standalone. Is that reasonable? I think this could be fixed by baking it into the cc-cflags as is done for compiler-rt here. https://github.com/NixOS/nixpkgs/blob/176015fc743583e30581c23bfda2bf848dd4d67d/pkgs/development/compilers/llvm/16/default.nix#L257	13:54:38
p14	Seems someone already beat me to it: https://github.com/NixOS/nixpkgs/issues/201591 / https://github.com/NixOS/nixpkgs/pull/220520	14:13:40
trofi	yeah, i think mingw compilers have a similar problem and don't supply enough libraries to compile hello world without manual fiddling	21:00:38

Show newer messages

Back to Room ListRoom Version: 9