On Mon, Feb 13, 2023 at 09:36:17PM +0000, Kaelyn wrote: > ------- Original Message ------- > On Monday, February 13th, 2023 at 8:04 PM, Efraim Flashner > <efr...@flashner.co.il> wrote: > > > > > > On Sun, Feb 12, 2023 at 06:29:04PM +0000, Kaelyn wrote: > > > > > Hi, > > > > > > ------- Original Message ------- > > > On Sunday, February 12th, 2023 at 5:08 PM, Andreas Enge andr...@enge.fr > > > wrote: > > > > > > > Am Sun, Feb 12, 2023 at 12:58:06PM +0100 schrieb Julien Lepiller: > > > > > > > > > And I was able to rebuild (with --check) patch-mesboot. The error > > > > > looks > > > > > a lot like https://issues.guix.gnu.org/49985. We should fix that > > > > > indeed > > > > > :) > > > > > > > > Ah indeed, that looks like deal breaking; maybe someone from MES can > > > > have > > > > a look? > > > > > > > > What is the magic incantation with double "@@" to build this package? > > > > Ah, here we go, for reference to self: > > > > guix build -e '(@@ (gnu packages commencement) patch-mesboot)' > > > > > > > > Andreas > > > > > > While not directly related to the patch-mesboot error, I want to mention > > > that there is also https://issues.guix.gnu.org/58719 blocking i686 builds > > > on core-updates (and x86_64 builds of certain packages like wine64, which > > > has i686 dependencies) since the update to glibc 2.35. > > > > > > It may also need assistance from the MES folks to fix, since the error > > > message is about an undefined symbol in glibc-mesboot's libpthread.so.0: > > > > > > make[2]: Entering directory > > > '/tmp/guix-build-file-5.44.drv-0/file-5.44/magic' > > > ../src/file -C -m magic > > > /tmp/guix-build-file-5.44.drv-0/file-5.44/src/.libs/file: symbol lookup > > > error: > > > /gnu/store/s4yd6ibxsh5q1j9ipygb9vpjj4g00wc9-glibc-mesboot-2.16.0/lib/libpthread.so.0: > > > undefined symbol: h_errno, version GLIBC_PRIVATE > > > make[2]: *** [Makefile:863: magic.mgc] Error 127 > > > > > > Cheers, > > > Kaelyn > > > > > > I think I found where this is coming from. %boot3-inputs added > > ld-wrapper-boot3 but didn't remove ld-wrapper-0, which pulled in > > glibc-mesboot. I'm testing out removing ld-wrapper-0 from %boot3-inputs > > to see if that's enough to make that final file build. Hopefully it'll > > also fix the final tar for i686, which I found was also failing for me. > > Interesting! Since my last email, I was able to fix the issue with file by > adding "--disable-xzlib" to the file package in gnu/packages/commencement.scm > (after discovering it when noticing "--disable-bzlib" was being passed to the > configure script), but hadn't sent in a patch yet because I hit a subsequent > test failure while building tar. I thought to disable xz support because I > traced the source of the glibc-mesboot libpthread.so in the error message to > xz-mesboot being detected by the configure script and linked in even though > file itself was being linked against a newer glibc and had no explicit > dependencies. (I think the error after upgrading to glibc 2.35 from 2.33 was > an abi compatibility between the newer glibc and the old pthread being pulled > in via xz-mesboot.) > > Cheers, > Kaelyn
I ended up going a different route and moving xz from the finalize packages to an actual xz-final and replacing xz-bootstrap/xz-mesboot in %boot6-inputs. I also tracked down the issue in tar and adjusted the testsuite so it shouldn't be a problem on 32-bit systems. -- Efraim Flashner <efr...@flashner.co.il> אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted
signature.asc
Description: PGP signature