#466 closed defect (invalid)
GCC compiled with --enable-__cxa_atexit causes segfaults in uic (part -f qt)
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Book | Version: | CVS |
Severity: | normal | Keywords: | |
Cc: |
Description
I was unabl;e to compile KDElibs3.1RC5, the user interface compiler, part of QT, segfaulted when it exited. Solution was to recompile gcc without --enable-cxa_atexit, then glibc, then Xwindows. After that, everything went smoothly. I suggest removal of the option in the upcoming lfs book.
Change History (2)
comment:1 by , 22 years ago
comment:2 by , 22 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Invalidating the bug. Not an issue, must be an isolated incident.
Note:
See TracTickets
for help on using tickets.
I strongly object to this suggestion. It clearly goes against the documentation on the GCC web site at http://gcc.gnu.org/gcc-3.2/c++-abi.html
FWIW, I have recently compiled qt-3.1.0 and qt-3.1.1 as well as kdelibs-3.1rc5 and kdelibs-3.1rc6 without problem. Admittedly, my system isn't strictly by the book but the gcc is most certainly compiled with --enable-cxa_atexit.
I suggest you need to look elsewhere for the QT uic segfault problem. Is hard to say what the problem may be without a backtrace. But it smells like a miscompiled glibc from this angle. Maybe the fact you recompiled glibc made the problem go away? It would be interesting to see if you recompiled gcc with --enable-cxa_atexit then recompiled glibc then everything else and see if the problem still exists. In other words, I'm speculating that your recompile of glibc made the problem go away, and not omission of the --enable-cxa_atexit switch to gcc.