all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Mája Tomášek" <maya.tomasek@disroot.org>
Cc: 58249-done@debbugs.gnu.org
Subject: bug#58249: [PATCH] gnu: packages: qt: Fix qtbase-5 not building on gcc 11 or later
Date: Thu, 26 Jan 2023 11:40:30 -0500	[thread overview]
Message-ID: <87fsbxxn9d.fsf@gmail.com> (raw)
In-Reply-To: <87mt662uo1.fsf@disroot.org> ("Mája Tomášek"'s message of "Wed, 25 Jan 2023 22:03:58 +0100")

Hi,

Mája Tomášek <maya.tomasek@disroot.org> writes:

> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Hello,
>>
>> Mája Tomášek <maya.tomasek@disroot.org> writes:
>>
>> [...]
>>
>>> I don't know, it is a hidden bug that is likely to cause quite a big
>>> problem once Guix moves to GCC 11 or later, as many apps probably won't update to
>>> Qt 6.
>>
>> The best solution may be to update our Qt 5 version; would you like to
>> give it a try?  Other than being a lot of new hashes to update (for each
>> qt5 component), it should be relatively low risk (with regards to
>> breaking existing Qt 5 packages).
>>
>> -- 
>> Thanks,
>> Maxim
>
> I haved looked into it, and guix has already shipped a patched version
> :)
>
> This can be closed now.
> Maya

Great, thanks for the follow-up.

I'm closing this by replying to 58249-done@debbugs.gnu.org in CC.

-- 
Thanks,
Maxim




      reply	other threads:[~2023-01-26 16:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-02 14:22 [bug#58249] [PATCH] gnu: packages: qt: Fix qtbase-5 not building on gcc 11 or later guix-patches--- via
2023-01-03 22:18 ` Maxim Cournoyer
2023-01-08 22:49   ` guix-patches--- via
2023-01-10 15:07     ` Maxim Cournoyer
2023-01-25 21:03       ` guix-patches--- via
2023-01-26 16:40         ` 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

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

  git send-email \
    --in-reply-to=87fsbxxn9d.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=58249-done@debbugs.gnu.org \
    --cc=maya.tomasek@disroot.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.