summaryrefslogtreecommitdiff
path: root/dev-cpp/glibmm/files
AgeCommit message (Collapse)Author
2024-12-12dev-cpp/glibmm: remove method that is not used any whereDenis Pronin
Closes: https://bugs.gentoo.org/945375 Signed-off-by: Denis Pronin <dannftk@yandex.ru> Closes: https://github.com/gentoo/gentoo/pull/39525 Signed-off-by: Sam James <sam@gentoo.org>
2019-01-03dev-cpp/glibmm: remove oldMart Raudsepp
Package-Manager: Portage-2.3.52, Repoman-2.3.12 Signed-off-by: Mart Raudsepp <leio@gentoo.org>
2018-05-22dev-cpp/glibmm: Fix build with GCC 8Jan Kundrát
Patch taken from upstream and adapted to actually touch the pregenerated file shipped with the release tarbal as well. That code appears to have been always wrong, with no chance to build. This probably means that GCC 8 is suddenly being detected in some other way, making the code use that include file which was previously apparently kept unused. But anyway, upstream killed that include in a later release, so let's just let this build and watch the eventual breakage. Upstream says: > Fixed in the glibmm-2-54 branch. No fix is necessary in the master > branch. The threads.hg and threads.h files don't exist there. Closes: https://bugs.gentoo.org/654776 Bug: https://bugzilla.gnome.org/show_bug.cgi?id=791711 Closes: https://github.com/gentoo/gentoo/pull/8324
2016-04-17dev-cpp/glibmm: Drop oldPacho Ramos
Package-Manager: portage-2.2.28
2015-12-12dev-cpp/glibmm: Version bump, fix build failure with gcc-4.7 (bug #566426 by ↵Pacho Ramos
Émeric Maschino) Package-Manager: portage-2.2.24