From: Marius Bakke <mbakke@fastmail.com>
To: John Soo <jsoo1@asu.edu>, 39758-done@debbugs.gnu.org
Subject: bug#39758: [PATCH] Add qtbase-patched. (Fix QTBUG-81715)
Date: Mon, 24 Feb 2020 18:16:14 +0100 [thread overview]
Message-ID: <87sgiz52jl.fsf@devup.no> (raw)
In-Reply-To: <CAKf5CqV-R5atuN58O_R+Jt2WK0JwSbY9cYPc=39u2VG8iYfccQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]
John Soo <jsoo1@asu.edu> writes:
> Hi Guix,
>
> There is a known issue in qtbase 5.12.7 where the cmake macros shipped
> with qt do not work when paths include dots. This broke freecad and
> maybe others.
Thanks! I've pushed the patches with a few modifications in
e2546bb472b6285a8856cacf686c5e0ce9bb62c5 and
3c60d85f313f910282ed884eead80061faf6ee78.
I will move the patch to the regular qtbase package on the 'staging'
branch later to avoid the custom variant.
> I am not sure how to figure out other broken packages, if they need to
> use the patched-qtbase.
Typically you'd have to do 'guix refresh -l qtbase' and copy-paste the
package list to a 'guix build' invokation. IWBN to have a single
command for that.
[...]
> From 92ba3b59a2ff1dd6b4078c649a468fa208b47a59 Mon Sep 17 00:00:00 2001
> From: John Soo <jsoo1@asu.edu>
> Date: Fri, 21 Feb 2020 21:14:57 -0800
> Subject: [PATCH 3/4] gnu: freecad. Fix build failures.
>
> * gnu/packages/engineering.scm (freecad): [supported-systems] Only support aarch64 and
> x86_64-linux, [inputs] use qtbase-patched instead of qtbase.
I dropped the [supported-systems] change as it seems unrelated to the
qtbase problem. Could you submit it as a separate patch, ideally with a
comment that explains why we do it (i.e. "upstream only supports
64-bit platforms")?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-02-24 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 17:41 [bug#39758] [PATCH] Add qtbase-patched. (Fix QTBUG-81715) John Soo
2020-02-24 17:16 ` Marius Bakke [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=87sgiz52jl.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=39758-done@debbugs.gnu.org \
--cc=jsoo1@asu.edu \
/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.