Date: Wed, 01 Mar 2023 19:42:35 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 269637] sysutils/nix: build fails - linker issues - undefined symbols from AWS libs Message-ID: <bug-269637-227-DHoo6GDw7V@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-269637-227@https.bugs.freebsd.org/bugzilla/> References: <bug-269637-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D269637 John Hein <jcfyecrayz@liamekaens.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #240518|text/x-matlab |text/plain mime type| | --- Comment #5 from John Hein <jcfyecrayz@liamekaens.com> --- Created attachment 240518 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D240518&action= =3Dedit [backtrace] i386 core dump for a 'nix flake' test FYI, while 'make test' on amd64 passed, it did not on i386. Attached is a backtrace of a core file produced by 'nix flake metadata flake1' in tests/flakes/flakes.sh I don't necessarily think this failure on i386 is a show stopper for updati= ng to the latest nix, it's worth noting. I don't know if the old nix worked on i386 either (I could never build it with the latest versions dependencies - maybe it used to build on i386 with old aws-sdk-cpp, for instance?). I'll = try to dig in and find the root cause at some point. Maybe setting TEST_BROKEN_i386 is the appropriate course of action for now. It may be th= at the test failure is an indication that the tool is broken on i386 entirely.= I don't know yet. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-269637-227-DHoo6GDw7V>