unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Kaelyn <kaelyn.alexi@protonmail.com>
Cc: 58719-done@debbugs.gnu.org
Subject: bug#58719: core-updates: Build failure for file on i686-linux
Date: Tue, 19 Dec 2023 11:38:44 -0500	[thread overview]
Message-ID: <87v88u5eqz.fsf@gmail.com> (raw)
In-Reply-To: <V-HBQCvGYSJi9LJ6SIFogNfwmuE-gaw2m4whHH0wOfLtammFmxElaTbhFfSdJkqaTLs6kqJLmwfxlD-8QObIwZcMLEBXtvBhABjykAoUp5E=@protonmail.com> (Kaelyn's message of "Mon, 18 Dec 2023 17:46:10 +0000")

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




      reply	other threads:[~2023-12-19 16:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22 16:03 bug#58719: core-updates: Build failure for file on i686-linux Kaelyn via Bug reports for GNU Guix
2023-02-12 18:02 ` 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 [this message]

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=87v88u5eqz.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=58719-done@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).