bug#58719: core-updates: Build failure for file on i686-linux

bug#58719: core-updates: Build failure for file on i686-linux

[Kaelyn via Bug reports for GNU Guix]

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

bug#58719: core-updates: Build failure for file on i686-linux

[Kaelyn via Bug reports for GNU Guix]

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.

bug#58719: core-updates: Build failure for file on i686-linux

[Maxim Cournoyer]

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.

-- 
Thanks,
Maxim

bug#58719: core-updates: Build failure for file on i686-linux

[Kaelyn via Bug reports for GNU Guix]

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.

Cheers,
Kaelyn

> 
> --
> Thanks,
> Maxim

bug#58719: core-updates: Build failure for file on i686-linux

[Maxim Cournoyer]

Hi,

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

> 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