[frameworks-kconfig] [Bug 387820] KConfigGui misbehave at runtime when link time optimizations are enabled

2022-12-09 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=387820 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO

[frameworks-kconfig] [Bug 387820] KConfigGui misbehave at runtime when link time optimizations are enabled

2022-11-24 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=387820 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular

[frameworks-kconfig] [Bug 387820] KConfigGui misbehave at runtime when link time optimizations are enabled

2022-11-10 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=387820 Justin Zobel changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|---

[frameworks-kconfig] [Bug 387820] KConfigGui misbehave at runtime when link time optimizations are enabled

2017-12-12 Thread Matthew Dawson
https://bugs.kde.org/show_bug.cgi?id=387820 --- Comment #3 from Matthew Dawson --- (In reply to Emmanuel Lepage Vallée from comment #2) > kconfigskeleton.cpp is part of KConfigGui, so if the private .h is part of > KConfigGui too, then there's no issue. Nothing from

[frameworks-kconfig] [Bug 387820] KConfigGui misbehave at runtime when link time optimizations are enabled

2017-12-12 Thread Emmanuel Lepage Vallée
https://bugs.kde.org/show_bug.cgi?id=387820 --- Comment #2 from Emmanuel Lepage Vallée --- kconfigskeleton.cpp is part of KConfigGui, so if the private .h is part of KConfigGui too, then there's no issue. Nothing from KConfigCore is involved. -- You are receiving this mail

[frameworks-kconfig] [Bug 387820] KConfigGui misbehave at runtime when link time optimizations are enabled

2017-12-12 Thread Matthew Dawson
https://bugs.kde.org/show_bug.cgi?id=387820 --- Comment #1 from Matthew Dawson --- Sorry if I misunderstand your proposed solution, but it sounds like KConfigCore will then need to make calls into KConfigGui, would require it to be linked together and defeat the purpose of