| Summary: | kde4bindings fails to build from source on architectures where qreal != double | ||
|---|---|---|---|
| Product: | [Unmaintained] bindings | Reporter: | Michael Casadevall <sonicmctails> |
| Component: | general | Assignee: | kde-bindings |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | lool |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Checks for PyQt_qreal_double ... | ||
|
Description
Michael Casadevall
2008-12-02 12:14:58 UTC
moved to bindings I'm not moving this bug to bindings is appropriate; this is an issue with kdelibs specifically, it just happens bindings has code that triggers the build failure. kplotaxis is a QWidget derived widget; the bug is occurring because its using double directly vs. qreal. Alternatively, if it is a binding specific problem, then the bug is in sip specifically since that's what generates the code, but as far as I can tell, placing data elements from KPlotAxis into a QList<qreal> is acceptable (aka, sip is generated proper code, it just happens that as long as kplotaxis is using double specifically vs. qreal, it will break on architectures that qreal != double). Created attachment 29543 [details]
Checks for PyQt_qreal_double ...
The main issue was caused by PyQt_qreal_double not being passed to sip during the generation of python-kde4 C files. The following patch fixes that, but the cmake code should probably be changed to use all the options set forth by SIP (unless this is done like this for a reason).
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! 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 bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |