| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| upstream_IPC-add-PATH_MAX-less-fallback-definition-for-MAX_PA.patch | [PATCH] IPC: add PATH_MAX-less fallback definition for MAX_PATH Define MAX_PATH also when PATH_MAX is not defined (e.g on GNU/Hurd). MAX_PATH is Windows constant, and it is used in this file only in a code path for Windows; because of this, the static fallback define should be good enough. |
Pino Toscano <toscano.pino@tiscali.it> | no | 2024-06-22 | ||
| upstream_QStorageInfo-Unix-fix-declaration-of-mnt-on-Hurd.patch | [PATCH] QStorageInfo/Unix: fix declaration of 'mnt' on Hurd Directly use the right type for it, after the Linux code was dropped. Fixes commit 543ae6e6a43519b9fca6758c4a8c78625fcb2c86. |
Pino Toscano <toscano.pino@tiscali.it> | no | 2024-10-06 | ||
| Add-SH-detection.patch | Add SH description Upstream processes archs from time to time and tends to disable those that they do not know wether they are working or not. . SH is working on Debian, so as an intermediate measure re enable it here. |
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> | no | debian | ||
| use_float16_only_with_sse2.patch | use _Float16 only when SSE2 is enabled The GCC documentation [1] says: “On x86 targets with SSE2 enabled, GCC supports half-precision (16-bit) floating point via the _Float16 type”. . On non-SSE2 x86 (such as Debian i386 baseline [2]), __FLT16_MAX__ is defined starting with GCC 14 [3], however any non-trivial use of the _Float16 type results in an error: . error: operation not permitted on type ‘_Float16’ without option ‘-msse2’ . which makes some packages fail to build on i386 architecture [4]. . [1]: https://gcc.gnu.org/onlinedocs/gcc/Half-Precision.html [2]: https://wiki.debian.org/ArchitectureSpecificsMemo#i386-1 [3]: https://gcc.gnu.org/g:9a19fa8b616f83474c35cc5b34a3865073ced829 [4]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076986 |
Dmitry Shachnev <mitya57@debian.org> | yes | 2024-08-01 | ||
| remove_privacy_breaches.diff | remove non-used privacy-breach code This code makes Lintian unhappy. But we are really not using it, it only gets inserted when building the online doc. Anyways the best way to calm down Lintian is to simply remove it. |
Lisandro Damián Nicanor Pérez Meyer <lisandro@debian.org> | not-needed | 2015-02-18 | ||
| build_path_embedded_qtbuildinternalsextra_cmake.patch | [PATCH] cmake/QtBuildInternalsExtra.cmake.in: Patch out embedded build path. The original build path should not be needed in the shipped package, and causes reproducibility issues when built in different paths. https://reproducible-builds.org/docs/build-path/ |
Vagrant Cascadian <vagrant@reproducible-builds.org> | no | 2022-02-25 | ||
| cross.patch | no | |||||
| remove_rpath_from_examples.patch | remove RPATH/RUNPATH from examples' binaries. On Debian the examples are built against system's libraries, so there is no need to set RPATH/RUNPATH. |
Lisandro Damián Nicanor Pérez Meyer <lisandro@debian.org> | not-needed | 2024-02-15 | ||
| forkfd_grow_stack_upwards_on_hppa.patch | Change how stack grows on HPPA. On HPPA stack grows upwards. This patch introduces this change for this 3rd party code. |
John David Anglin <dave.anglin@bell.net> | no | debian | 2023-07-28 | |
| enable_skip_plugins.patch | Enable skipping plugins search at build time. This patch sets QT_SKIP_AUTO_PLUGIN_INCLUSION and QT_SKIP_AUTO_QML_PLUGIN_INCLUSION to ON by default, thus avoiding unnecesary build dependencies on plugins. . The variables can still be set to OFF by the user at build time, allowing them to find the packages if necessary. But if you need so for a Debian package please reach the Qt maintainers first. We want to know why you need to do so. Thanks in advance! |
Lisandro Damián Nicanor Pérez Meyer <lisandro@debian.org> | not-needed | |||
| armv4.diff | support ARMv4 architecture, needed for armel builds | Dmitry Shachnev <mitya57@debian.org> | no | 2016-07-01 |