From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tobias Geerinckx-Rice Subject: Re: Qt build problems after bump to 5.12.7 Date: Thu, 20 Feb 2020 18:43:39 +0100 Message-ID: <87o8ttxigk.fsf@nckx> References: Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:42982) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j4pr6-00023N-Nw for guix-devel@gnu.org; Thu, 20 Feb 2020 12:43:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j4pr5-0004et-0s for guix-devel@gnu.org; Thu, 20 Feb 2020 12:43:20 -0500 Received: from tobias.gr ([2001:470:7405::1]:37508) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1j4pr4-0004dz-JR for guix-devel@gnu.org; Thu, 20 Feb 2020 12:43:18 -0500 Received: by tobias.gr (OpenSMTPD) with ESMTP id fe48fef9 for ; Thu, 20 Feb 2020 17:43:15 +0000 (UTC) Received: by submission.tobias.gr (OpenSMTPD) with ESMTPSA id ce875fb2 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Thu, 20 Feb 2020 17:43:15 +0000 (UTC) In-reply-to: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable John Soo =E5=86=99=E9=81=93=EF=BC=9A > I was looking into the failing freecad build and I found the=20 > 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=20 > contain dots: > > https://bugreports.qt.io/browse/QTBUG-81715 > > I think this probably effects more cmake based qt projects than=20 > just freecad. > The qt-build-system is based on cmake and many of the store=20 > 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=20 the fix[0] to a separate qtbase/fixed package, and use it (on=20 master) in all packages that currently fail to build because of=20 this bug. Once Qt 5.12.8 comes out in April (or we upgrade=20 everything to 5.14), the /fixed variant can be removed on the=20 staging branch. 2. If fewer than 300 qtbase dependents currently build=20 successfully: apply the patch directly to qtbase on master. Newly=20 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 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEfo+u0AlEeO9y5k0W2Imw8BjFSTwFAl5OxUsACgkQ2Imw8BjF STyrJg/+MeB6+5U1ZSUKFqzQ78nh4elzn+UBPjs7Wcn/vD8CnE8ev6xFXtWGugD7 VWuWK7YHHWR8pMcahqCFHuBBmBdVVhH+/JuLSpPn8oGQ45bEDXJPIlvtJJk6GPS6 I+N5PQnh3/WhW+uU4Jo5ymz0tfEkF4or6ycyr3Q37tuTbYt9BoiINoIlbFnh1Rp3 WDSzQXn5rFzqnBGfXd8qSsTkCg1zKcGlaR2FGvUnutKCrliXnVCvtWSSY74TNV2c 5JEkPBITQzZE3bA+lXKyBy5wiBIGjC5uHORtw0JEU7N3KfGyhTJASYyn+hP7wt/B EnTr5SI3qTKvSPZgQ7eip2Ch8cd8qga97LISkXEHWbeNrbBaiIEujetRPDCfCQ4V IImRSyhUxgb4lgqGcRLq/BhSt3OgRtrh9EjI5U/UbZJ1oh/vq+yVng+5DkxrVuSq ubRi4domPAgWdu0e1+Zfan5i2n2k0GuUb+JXFiNCG4drmrH5Y5/Wt/RjE4rZlSYR BetQjglSx3VikiMxoixBD4EanaaxE6dPfiAleQMQCg5LcmOxlm19T1ZPZlV3y5Ko OP545XW2zLUg6tSJ3aDrMquxoSffKfDnR457H4vy+OTp4Br14OGpSVJkThE0vnmn 1hpRQbPn81y4WGxJPcC32nEemjNWGAqj1TZYDClrVnh/yLqvwJA= =eKRS -----END PGP SIGNATURE----- --=-=-=--