Bug 145991

Summary: {standard input}:221200: Error: bad register name `%'
Product: [Developer tools] bindings Reporter: oneforall <oneforall59>
Component: generalAssignee: kde-bindings
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: chrisburel
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:

Description oneforall 2007-05-26 16:52:13 UTC
Version:           3.5.7 (using KDE KDE 3.5.7)
Installed from:    Compiled From Sources
Compiler:          gcc 4.1.2 glibc 2.5
OS:                Linux

sipqtpart0.cpp:11894: warning: dereferencing type-punned pointer will break strict-aliasing rules
sipqtpart0.cpp:11895: warning: dereferencing type-punned pointer will break strict-aliasing rules
{standard input}: Assembler messages:
{standard input}:220295: Warning: end of file not at end of a line; newline inserted
{standard input}:221200: Error: bad register name `%'
g++: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[3]: *** [sipqtpart0.o] Error 1
make[3]: Leaving directory `/tmp/kdebindings-3.5.7/python/pyqt/qt'
make[2]: *** [install] Error 2
make[2]: Leaving directory `/tmp/kdebindings-3.5.7/python/pyqt'
make[1]: *** [install] Error 2
make[1]: Leaving directory `/tmp/kdebindings-3.5.7/python'
make: *** [install-recursive] Error 1
rmdir: /tmp/package-kdebindings/usr/share: Directory not empty

it continues to compile and I don't see a ignore. then it gets to the same sipqtpart0.cpp:11895: warning: dereferencing type-punned pointer will break again and then the error
Comment 1 Pino Toscano 2007-05-26 19:57:21 UTC
*** Bug 145993 has been marked as a duplicate of this bug. ***
Comment 2 Pino Toscano 2007-05-26 19:57:28 UTC
*** Bug 145994 has been marked as a duplicate of this bug. ***
Comment 3 Andrew Crouthamel 2018-11-02 04:22:26 UTC
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!
Comment 4 Andrew Crouthamel 2018-11-16 02:41:31 UTC
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?

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2022-12-07 00:24:03 UTC
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!
Comment 6 Chris Burel 2022-12-07 14:16:08 UTC
Seeing as the last release to the KDE 3 series was 14 years ago, I'm going to resolve this as unmaintained.