core-updates: Build failure for file on i686-linux

  • Done
  • quality assurance status badge
Details
2 participants
  • Kaelyn
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Kaelyn
Severity
normal
K
K
Kaelyn wrote on 22 Oct 2022 18:03
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)
lhkbHhamQN3tZIzaVHJ_RV5epwh3KUv9JxfX4JIOMd_GJGCwcsK9XcfzICxJvy7FRPwqwdyvz2koR5AP6zfwC_NNaPlfcSfUVtp3gUnDOfo=@protonmail.com
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
K
K
Kaelyn wrote on 12 Feb 2023 19:02
(name . 58719@debbugs.gnu.org)(address . 58719@debbugs.gnu.org)
erAKS3xObBjFjjRZRdu8QcPuPkuqvLTS392w9YiKJ7GV5rONzPkiABBxraO7CHIlfDYUw2J6opn8X-KxEyy78mdSp4mr8rN6Y1P6VQTHvS8=@protonmail.com
As a bit of followup, this bug still exists with the latest core-updates commit. This not only affects i686 systems, but also some x86_64 packages like wine/wine64 which require a 32-bit build in addition to a 64-bit one.
M
M
Maxim Cournoyer wrote on 17 Dec 2023 23:15
Re: bug#58719: core-updates: Build failure for file on i686-linux
(name . Kaelyn)(address . kaelyn.alexi@protonmail.com)(name . 58719@debbugs.gnu.org)(address . 58719@debbugs.gnu.org)
877clc79wu.fsf@gmail.com
Hello,

Kaelyn <kaelyn.alexi@protonmail.com> writes:

Toggle quote (5 lines)
> As a bit of followup, this bug still exists with the latest
> core-updates commit. This not only affects i686 systems, but also some
> x86_64 packages like wine/wine64 which require a 32-bit build in
> addition to a 64-bit one.

Is this problem known upstream? If not, we should forward it to them.

--
Thanks,
Maxim
K
K
Kaelyn wrote on 18 Dec 2023 18:46
(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)(name . 58719@debbugs.gnu.org)(address . 58719@debbugs.gnu.org)
V-HBQCvGYSJi9LJ6SIFogNfwmuE-gaw2m4whHH0wOfLtammFmxElaTbhFfSdJkqaTLs6kqJLmwfxlD-8QObIwZcMLEBXtvBhABjykAoUp5E=@protonmail.com
Hi Maxim,

On Sunday, December 17th, 2023 at 2:15 PM, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:

Toggle quote (13 lines)
>
> Hello,
>
> Kaelyn kaelyn.alexi@protonmail.com writes:
>
> > As a bit of followup, this bug still exists with the latest
> > core-updates commit. This not only affects i686 systems, but also some
> > x86_64 packages like wine/wine64 which require a 32-bit build in
> > addition to a 64-bit one.
>
>
> Is this problem known upstream? If not, we should forward it to them.

Thank you for the follow-up. I'm fairly certain this bug is outdated and can be closed now (it was from a previous iteration of core-updates). I don't remember what fixed it (possibly the update of file from 5.42 to 5.44), but the issue did get resolved by the time core-updates was merged and I haven't run into issues building wine since then.

Cheers,
Kaelyn

Toggle quote (4 lines)
>
> --
> Thanks,
> Maxim
M
M
Maxim Cournoyer wrote on 19 Dec 2023 17:38
(name . Kaelyn)(address . kaelyn.alexi@protonmail.com)(address . 58719-done@debbugs.gnu.org)
87v88u5eqz.fsf@gmail.com
Hi,

Kaelyn <kaelyn.alexi@protonmail.com> writes:

Toggle quote (24 lines)
> Hi Maxim,
>
> On Sunday, December 17th, 2023 at 2:15 PM, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>
>>
>> Hello,
>>
>> Kaelyn kaelyn.alexi@protonmail.com writes:
>>
>> > As a bit of followup, this bug still exists with the latest
>> > core-updates commit. This not only affects i686 systems, but also some
>> > x86_64 packages like wine/wine64 which require a 32-bit build in
>> > addition to a 64-bit one.
>>
>>
>> Is this problem known upstream? If not, we should forward it to them.
>
> Thank you for the follow-up. I'm fairly certain this bug is outdated
> and can be closed now (it was from a previous iteration of
> core-updates). I don't remember what fixed it (possibly the update of
> file from 5.42 to 5.44), but the issue did get resolved by the time
> core-updates was merged and I haven't run into issues building wine
> since then.

Excellent, thanks for the reply. I'm closing this report by replying in
CC to 58719-done@debbugs.gnu.org :-).

--
Thanks,
Maxim
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 58719@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 58719
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch