Bug#928344: marked as done (qtchooser: Please build with -D_FILE_OFFSET_BITS=64)
Your message dated Fri, 03 May 2019 16:33:36 +0000
with message-id <E1hMb7w-000IS3-8y@fasolo.debian.org>
and subject line Bug#928344: fixed in qtchooser 66-2
has caused the Debian Bug report #928344,
regarding qtchooser: Please build with -D_FILE_OFFSET_BITS=64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
928344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928344
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: qtchooser
Version: 66-1
Severity: important
User: debian-68k@lists.debian.org
Usertags: m68k
Hello!
A change recently introduced to glibc with version 2.28 [1] has broken
some applications running in qemu-user when emulating 32-bit architectures
on 64-bit platforms [2].
As a result, any 32-bit application compiled without -D_FILE_OFFSET_BITS=64
will behave erratically when running on qemu-user on a 64-bit platform,
one affected package was dash [3] which has already been fixed although the
problem didn't show there in the context of qemu.
qtchooser suffers from this problem as well and the sympton is that running
qmake, for example, results in qtchooser unable to find the Qt5 installation:
(sid-sh4-sbuild)root@epyc:/# QT_SELECT=5 qmake
qmake: could not find a Qt installation of '5'
(sid-sh4-sbuild)root@epyc:/#
Luckily, there is a simply workaround which is adding the following to debian/
rules which results in qtchooser being built with -D_FILE_OFFSET_BITS=64:
export DEB_CXXFLAGS_MAINT_APPEND := -D_FILE_OFFSET_BITS=64
A locally built version of the package with the fix applied works correctly
again:
(sid-sh4-sbuild)root@epyc:/# dpkg -i qtchooser_66-1+qemu_sh4.deb
(Reading database ... 45935 files and directories currently installed.)
Preparing to unpack qtchooser_66-1+qemu_sh4.deb ...
Unpacking qtchooser (66-1+qemu) over (66-1) ...
Setting up qtchooser (66-1+qemu) ...
Processing triggers for man-db (2.8.5-2) ...
(sid-sh4-sbuild)root@epyc:/# QT_SELECT=5 qmake
Usage: /usr/lib/qt5/bin/qmake [mode] [options] [files]
(...)
-nocache Don't use a cache file [makefile mode only]
-nodepend Don't generate dependencies [makefile mode only]
-nomoc Don't generate moc targets [makefile mode only]
-nopwd Don't look for files in pwd [project mode only]
(sid-sh4-sbuild)root@epyc:/#
I would highly recommend to include this fix and even try to get it included
for Buster as otherwise anyone running Qt-related tools inside qemu-user
for 32-bit applications on 64-bit targets on Buster will run into this bug
(e.g., people running an armel chroot on x86_64).
Adrian
> [1] https://sourceware.org/git/?p=glibc.git;a=commit;h=298d0e3129c0b5137f4989275b13fe30d0733c4d
> [2] https://sourceware.org/bugzilla/show_bug.cgi?id=23960
> [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916255
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Source: qtchooser
Source-Version: 66-2
We believe that the bug you reported is fixed in the latest version of
qtchooser, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 928344@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Shachnev <mitya57@debian.org> (supplier of updated qtchooser package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 03 May 2019 19:08:24 +0300
Source: qtchooser
Architecture: source
Version: 66-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>
Changed-By: Dmitry Shachnev <mitya57@debian.org>
Closes: 928344
Changes:
qtchooser (66-2) unstable; urgency=medium
.
[ Simon Quigley ]
* Change my email to tsimonq2@debian.org now that I am a Debian Developer.
* Bump Standards-version to 4.3.0, no changes needed.
.
[ Dmitry Shachnev ]
* Build with large file support (closes: #928344).
Checksums-Sha1:
626e179d335b239709d5427b82fcc8dfd6a68668 2123 qtchooser_66-2.dsc
70a0793855ce5dd3787901c4faaa90071a084201 6308 qtchooser_66-2.debian.tar.xz
1721b7638ab0ce430c28837c849dcf57ffbbfce1 10155 qtchooser_66-2_source.buildinfo
Checksums-Sha256:
f66fe338edb8d9e4d3bea3d850cc7bf6d5aaa1c853108c24b0130fd2e0e92378 2123 qtchooser_66-2.dsc
50890b26cf85b5132b76a571989101b2f9e05b116f2f58e458525286d6c55e52 6308 qtchooser_66-2.debian.tar.xz
e2eabc4b7e22834459ba7c44ff9de8774ce9c487e067efb4c5016c62619491bd 10155 qtchooser_66-2_source.buildinfo
Files:
db5625d80b79ef339fbc15a920ad243a 2123 libdevel optional qtchooser_66-2.dsc
be29c161dce1a7037e3a55b0c76a290e 6308 libdevel optional qtchooser_66-2.debian.tar.xz
9f50501866ce8f848eecd331c86f9ddd 10155 libdevel optional qtchooser_66-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJHBAEBCgAxFiEE8kKZ/xu8kBi5BqTLYCaTbS8ciuAFAlzMaJ8THG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBgJpNtLxyK4LhIEAC7IRaQnCgIZTUMc3Ofebw0owpiS0ew
dmImWw6Q2cSmEgl78bHPv8j3qrNghsh5BhNPXu2qRIylHeOP0+VNlfI43vCOUkRK
6nytYaU5o+EZTIjJ0UvsF6SrNHpqN4tnWhR0W4i3r0HgAO0p92MtaLpBMGsrfUCU
gLduh0VeZczcSs735cC2tfhwEhHKWMAZ0XHPa4LeIev57QPR+1PaS+lc+XOlOZH4
7SrBMvXnmn1rvQF5N1dd9aAcqY9J1pMZavsDY1WPvKeAdIWf16KIKQ4MPZeIezG2
hiIhAl32uO0vD94AEtuWhw5+geBpTMMwlcsmOdSx/wqLM2r9qqqdILj6QYpynLfv
NKZf4Ur5dq1F/Ci+37L6oqr7RKuqH5SwccPcVkHRTaIzaqVyzR6BnH85zY440hzL
Ik94jr4iYGqsIWN0UwwmwDm9w6aflGCHPK08vVq2nch+lHMqXDaeaggnxUMpDBzm
nTeLF50qt2vHCn0GDmvwcsGZ5agmxeWUQ7AcS2mYDBPmtxWEJsHB5sMbjmPMzBvL
Q04L8L9zvZ4bP+UcTclJG/EXiVIVW9+gJ43KuGAJy8Y/HqHmocX25yjQti9U4M7g
6qfgw5wAXR+BPVgH7Br2Q3MM8oseCcvsm6X5epe3myG/b7AsxyHTZSsTEy9iKdxR
sEAUE8koj0FbBw==
=fg9H
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: