Tim, Darrell, All, Last night I started an i686 build run. During that run, several packages failed that had just built without issue on x86_64. At first it just looked like a cmake/library issue, but comparing the build failures, there is some common thread running between them that I cannot put my finger on. I need help to determine what the issue is. Most errors I can poke around at enough to figure out, but this one looks strange enough, I would like a second pair of eyes on it. Specifically, it looks to me like any time a link is called involving something openGL related, the build fails with a sting of "undefined reference to `TQGLWidget::" messages. Examples: tdeartwork: <snip> CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o: In function `EuphoriaWidget::staticMetaObject()': Euphoria.cpp:(.text+0x389): undefined reference to `TQGLWidget::staticMetaObject()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o: In function `EuphoriaWidget::~EuphoriaWidget()': Euphoria.cpp:(.text+0xd45): undefined reference to `TQGLWidget::~TQGLWidget()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o: In function `EuphoriaWidget::EuphoriaWidget(TQWidget*, char const*)': Euphoria.cpp:(.text+0x2b5e): undefined reference to `TQGLWidget::TQGLWidget(TQWidget*, char const*, TQGLWidget const*, unsigned int)' <snip> amarok: <snip> analyzers/libanalyzers.a(analyzerbase.cpp.o): In function `Analyzer::Base3D::tqt_emit(int, TQUObject*)': analyzerbase.cpp:(.text+0x1e7): undefined reference to `TQGLWidget::tqt_emit(int, TQUObject*)' analyzers/libanalyzers.a(analyzerbase.cpp.o): In function `Analyzer::Base3D::tqt_property(int, int, TQVariant*)': analyzerbase.cpp:(.text+0x21f): undefined reference to `TQGLWidget::tqt_property(int, int, TQVariant*)' analyzers/libanalyzers.a(analyzerbase.cpp.o): In function `Analyzer::Base3D::staticMetaObject()': analyzerbase.cpp:(.text+0x391): undefined reference to `TQGLWidget::staticMetaObject()' <snip> Not having any logical explanation for the failures and there being no explicit library missing, I went back and rebuilt everything again. from tqt3 to kdebase. Now recall, the build last night proceeded without error from tqt3 to kdebase, so I should simply be rebuilding the exact same code as was done in: makepkg --> SUCCEEDED for tqt3 at Jan 27 20:11:18 makepkg --> SUCCEEDED for tqtinterface at Jan 27 20:13:07 makepkg --> SUCCEEDED for arts at Jan 27 20:16:27 makepkg --> SUCCEEDED for dbus-tqt at Jan 27 20:16:34 makepkg --> SUCCEEDED for dbus-1-tqt at Jan 27 20:16:56 makepkg --> SUCCEEDED for tqca-tls at Jan 27 20:17:02 makepkg --> SUCCEEDED for libart-lgpl at Jan 27 20:17:21 makepkg --> SUCCEEDED for avahi-tqt at Jan 27 20:17:44 makepkg --> SUCCEEDED for libcaldav at Jan 27 20:18:07 makepkg --> SUCCEEDED for libcarddav at Jan 27 20:18:22 makepkg --> SUCCEEDED for sip4-tqt at Jan 27 20:19:09 makepkg --> SUCCEEDED for python-tqt at Jan 27 20:26:48 makepkg --> SUCCEEDED for tdelibs at Jan 27 20:51:11 makepkg --> SUCCEEDED for tdebase at Jan 27 21:16:07 <snip> makepkg --> FAILED for tdeartwork at Jan 27 22:05:12 After rebuilding the same packages again, (tqt3-tdebase) I can build tdeartwork without issue: makepkg --> SUCCEEDED for tdeartwork at Jan 28 15:16:25 Anybody else see this type of behavior? I rebuilt using parallel building again, so if it was to blame to begin with, it looks like this is some of the spurious type of errors that can occur. -- David C. Rankin, J.D.,P.E.