unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaelyn via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 58719@debbugs.gnu.org
Subject: bug#58719: core-updates: Build failure for file on i686-linux
Date: Sat, 22 Oct 2022 16:03:29 +0000	[thread overview]
Message-ID: <lhkbHhamQN3tZIzaVHJ_RV5epwh3KUv9JxfX4JIOMd_GJGCwcsK9XcfzICxJvy7FRPwqwdyvz2koR5AP6zfwC_NNaPlfcSfUVtp3gUnDOfo=@protonmail.com> (raw)

Hi,

Trying to build 'wine-minimal for x86-64 on core-updates, the following error is hit while building 'file for i686-linux:

/tmp/guix-build-file-5.42.drv-0/file-5.42/src/.libs/file: symbol lookup error: /gnu/store/wb8f0ydwl7458ixgsmx65x5ni54c7zgk-glibc-mesboot-2.16.0/lib/libpthread.so.0: undefined symbol: h_errno, version GLIBC_PRIVATE
make[2]: *** [Makefile:857: magic.mgc] Error 127
make[2]: Leaving directory '/tmp/guix-build-file-5.42.drv-0/file-5.42/magic'
make[1]: *** [Makefile:462: all-recursive] Error 1
make[1]: Leaving directory '/tmp/guix-build-file-5.42.drv-0/file-5.42'
make: *** [Makefile:371: all] Error 2

The build failure can be easily reproduced with `./pre-inst-env guix build --system=i686-linux file`, and I have bisected the failure on core-updates to commit 25b30622b4a77cd4b2965b9d62fa310a22413d54 "gnu: glibc: Update to 2.35.".

I suspect this may be causing many i686 failures on core-updates since `./pre-inst-env guix refresh -l file` reports 7732 packages that would have to be built to ensure 16065 dependent packages are rebuilt.

Cheers,
Kaelyn




             reply	other threads:[~2022-10-24  2:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22 16:03 Kaelyn via Bug reports for GNU Guix [this message]
2023-02-12 18:02 ` bug#58719: core-updates: Build failure for file on i686-linux Kaelyn via Bug reports for GNU Guix
2023-12-17 22:15   ` Maxim Cournoyer
2023-12-18 17:46     ` Kaelyn via Bug reports for GNU Guix
2023-12-19 16:38       ` Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='lhkbHhamQN3tZIzaVHJ_RV5epwh3KUv9JxfX4JIOMd_GJGCwcsK9XcfzICxJvy7FRPwqwdyvz2koR5AP6zfwC_NNaPlfcSfUVtp3gUnDOfo=@protonmail.com' \
    --to=bug-guix@gnu.org \
    --cc=58719@debbugs.gnu.org \
    --cc=kaelyn.alexi@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).