[From nobody Tue Sep 22 11:54:08 2026 Received: (at submit) by bugs.debian.org; 10 Mar 2019 13:47:43 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.2-bugs.debian.org_2005_01_02 (2018-09-13) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-17.4 required=4.0 tests=BAYES_00, FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, FROMDEVELOPER,HEADER_FROM_DIFFERENT_DOMAINS,MURPHY_DRUGS_REL8, PGPSIGNATURE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,RCVD_IN_SBLXBL, RCVD_IN_SBLXBL_CBL,SPF_PASS,TXREP,X_DEBBUGS_CC autolearn=ham autolearn_force=no version=3.4.2-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 43; hammy, 150; neutral, 26; spammy, 0. spammytokens: hammytokens:0.000-+--rw-r, 0.000-+--H*UA:1.10.1, 0.000-+--H*u:1.10.1, 0.000-+--H*u:2018-07-13, 0.000-+--H*UA:2018-07-13 Return-path: <mitya57@gmail.com> Received: from mail-lj1-f193.google.com ([209.85.208.193]) by buxtehude.debian.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <mitya57@gmail.com>) id 1h2ynm-0001nf-B0 for submit@bugs.debian.org; Sun, 10 Mar 2019 13:47:42 +0000 Received: by mail-lj1-f193.google.com with SMTP id d24so1734529ljc.12 for <submit@bugs.debian.org>; Sun, 10 Mar 2019 06:47:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=fukLTofzTdUhOWy1BXS/AR6PfQ7s0PJYaTefsmeLONk=; b=Chwj46vUpL338intpWLUaUKiOkAOtK2/1+35dgKr+CJWpGp5kFr4gg336KokX7Nzo5 MyBZfM/SoTm/lz9kNs9AXqSLs4TLScUrEh4LBb58qibeq4j8I6mXjqeBYJX+cwKOlcD3 RwFReE8FPAfDdDZyKvH3wZh13JtT0Xyf0JxE0Eanwda4MqN0An+Wn1xf6peBzzvqq7iK zFFOd/FHfqpKYsVASP/F3LJcoa9B8X71s21ipI6qRDsbZYmmw4vZZXi/LBPVvOyQtI/d ewnyvvd1YL2R27rTJHBzB0v6jMp93dnImQOE+avgGYITvz3smfHWG6rOQJ3M2CstjeCF t4Tg== X-Gm-Message-State: APjAAAXeFZRJ5lU1iKvV91DGXT+/VH2+Nyl55dg7eTAJETK2oC+3agsA lF0VkdNk264E91/0bY7hs5q1roLZ X-Google-Smtp-Source: APXvYqzhZExrnZ0UDqSoWU2V9ysQSOS1cMVGLT8whePW+05QYtXbuF1cSSzByvfkE7TxmjdDUb3mmQ== X-Received: by 2002:a2e:b014:: with SMTP id y20mr3514990ljk.116.1552225658374; Sun, 10 Mar 2019 06:47:38 -0700 (PDT) Received: from mitya57.me ([213.87.152.43]) by smtp.gmail.com with ESMTPSA id h23sm590221ljk.36.2019.03.10.06.47.37 for <submit@bugs.debian.org> (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Sun, 10 Mar 2019 06:47:37 -0700 (PDT) Date: Sun, 10 Mar 2019 16:47:35 +0300 From: Dmitry Shachnev <mitya57@debian.org> To: submit@bugs.debian.org Subject: dtkcore: Cross-builds incorrectly, built packages contain paths from build architecture Message-ID: <20190310134735.GA29646@mitya57.me> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline X-Debbugs-Cc: Helmut Grohne <helmut@subdivi.de> User-Agent: Mutt/1.10.1 (2018-07-13) Delivered-To: submit@bugs.debian.org --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Source: dtkcore Version: 2.0.9.17-1 Tags: patch User: helmutg@debian.org Usertags: rebootstrap Dear Maintainer, When one cross-builds dtkcore package the contents of built libdtkcore-dev are wrong: some files are installed into /usr/lib/${DEB_BUILD_MULTIARCH} instead of the expected /usr/lib/${DEB_HOST_MULTIARCH} path. E.g. in this example, it should be /usr/lib/arm-linux-gnueabihf instead of /usr/lib/x86_64-linux-gnu: $ dpkg-deb -c libdtkcore-dev_2.0.9.17-1_armhf.deb | grep mkspecs = =20 drwxr-xr-x root/root 0 2019-02-28 21:00 ./usr/lib/x86_64-linux-gn= u/qt5/mkspecs/ drwxr-xr-x root/root 0 2019-02-28 21:00 ./usr/lib/x86_64-linux-gn= u/qt5/mkspecs/features/ -rw-r--r-- root/root 2378 2019-02-26 02:56 ./usr/lib/x86_64-linux-gn= u/qt5/mkspecs/features/dtk_build.prf -rw-r--r-- root/root 1578 2019-02-26 02:56 ./usr/lib/x86_64-linux-gn= u/qt5/mkspecs/features/dtk_cmake.prf -rw-r--r-- root/root 376 2019-02-26 02:56 ./usr/lib/x86_64-linux-gn= u/qt5/mkspecs/features/dtk_lib.prf -rw-r--r-- root/root 4459 2019-02-26 02:56 ./usr/lib/x86_64-linux-gn= u/qt5/mkspecs/features/dtk_module.prf -rw-r--r-- root/root 3940 2019-02-26 02:56 ./usr/lib/x86_64-linux-gn= u/qt5/mkspecs/features/dtk_qmake.prf -rw-r--r-- root/root 1580 2019-02-26 02:56 ./usr/lib/x86_64-linux-gn= u/qt5/mkspecs/features/dtk_translation.prf drwxr-xr-x root/root 0 2019-02-28 21:00 ./usr/lib/x86_64-linux-gn= u/qt5/mkspecs/modules/ -rw-r--r-- root/root 471 2019-02-28 21:00 ./usr/lib/x86_64-linux-gn= u/qt5/mkspecs/modules/qt_lib_dtkcore.pri This happens because src/dtk_module.prf has "qmake -query" call, and qmake is the build architecture qmake by default. That subprocess call can be avoided at all, as the QT_HOST_DATA variable is built-in in qmake. A patch to fix that is attached. -- Dmitry Shachnev --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEE8kKZ/xu8kBi5BqTLYCaTbS8ciuAFAlyFFW4ACgkQYCaTbS8c iuBQgw//fqfq/e3XXYGQaCtlAPhJgKPM9WCbKTP2cvjZrzK+q4XsBWyb2piBKJB9 48s5YX3w9nn3Wj9TL+PxeMV1JQZ4IDdOaCakOe0AhEOEmB+apiwq/dwVU+S6C56m ilHDwZ/zGZiA7KBjln9GAgIGqo9mcSvZSsxTbTfBCSBZRxFuvThcUUF7yQ0hXphd 60MFaOybhn3g+GdXFKPvcVZLVNO0kppMQdWGupAmc4PFl6TAreH1qPWZ4Ev1jfCU fPOAp0YiK4eFDqEIwGuHWR5PaDspEFpgjqmJt/G+OP9vn+5Z/sGCFOv1XIPCO8oA PKXOBH4uQ3KWLVkeijd4+4WDJToUGgMqXiVstKLnWzfsZEMubMFIaOqwYVMfPlWk Pj0x2+AwDPVCFbaVRlz07mqod1GFmrc/PcTxawbf+RzP6KxOEK+vmSITBizJMze1 6vU7j6kIT0ppaFjZ6E5yb+kuaoLfmDYJITv2CiW+Khr+EFDb1/XrS7XassS8Gsa1 fbY7jw8gdy8P8HoDBSL7yiM2OpgLlxM3kQ9fifS4CUWp9RkyoW0Mj0reugUIs5gu MT8nkk8x+orYa69n951ovqrLbS19bR6YQhGFloPoKdoMf4G+FGYdYW4AfHn5N+yk 5OTgrKxwLsnvtN0fUErEjxSSDcTMmDPemy+UkyZG5zYglOEQr9w= =7kfp -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx-- ]