all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: guix-devel@gnu.org
Subject: Re: Qt build problems after bump to 5.12.7
Date: Thu, 20 Feb 2020 18:43:39 +0100	[thread overview]
Message-ID: <87o8ttxigk.fsf@nckx> (raw)
In-Reply-To: <CAKf5CqWzMR1CHSkSNK+pNuacDPXd2vUEmfpyJo4QxKt5RQrPQg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]

John Soo 写道:
> I was looking into the failing freecad build and I found the 
> following
> bug from the qt 5.12.7 known bugs page
> (https://wiki.qt.io/Qt_5.12.7_Known_Issues).
>
> - Qt-based CMake projects might fail if their build directories 
> contain dots:
>
>   https://bugreports.qt.io/browse/QTBUG-81715
>
> I think this probably effects more cmake based qt projects than 
> just freecad.
> The qt-build-system is based on cmake and many of the store 
> paths and
> build paths include semver version numbers.
>
> What should we do?

IIUC that this only affects qtbased packages:

1. If more than 300 qtbase dependents currently build fine: apply 
the fix[0] to a separate qtbase/fixed package, and use it (on 
master) in all packages that currently fail to build because of 
this bug.  Once Qt 5.12.8 comes out in April (or we upgrade 
everything to 5.14), the /fixed variant can be removed on the 
staging branch.

2. If fewer than 300 qtbase dependents currently build 
successfully: apply the patch directly to qtbase on master.  Newly 
succeeding builds don't count as rebuilds.

Does that make sense?

Kind regards,

T G-R

[0]: https://codereview.qt-project.org/c/qt/qtbase/+/288359

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2020-02-20 17:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 15:47 Qt build problems after bump to 5.12.7 John Soo
2020-02-20 17:43 ` Tobias Geerinckx-Rice [this message]
2020-02-21 17:10   ` John Soo
2020-02-22  5:23     ` John Soo
2020-02-22  5:51       ` John Soo
2020-02-23 17:44         ` John Soo

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=87o8ttxigk.fsf@nckx \
    --to=me@tobias.gr \
    --cc=guix-devel@gnu.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.