RESOLVED INVALID 13520
qmake/gmake sometimes has trouble properly resolving dependencies
https://bugs.webkit.org/show_bug.cgi?id=13520
Summary qmake/gmake sometimes has trouble properly resolving dependencies
Alexander Botero-Lowry
Reported 2007-04-27 02:44:42 PDT
Sometimes, if I rebuild the QT port without cleaning up the build dir I will get a failed build since not all the dependencies have been correctly noticed and recompiled (I've also seen this where after editing a file I had to delete the object file or it wouldn't be recompiled). An example of this might go something like: c++ -pthread -Wl,-rpath,/usr/home/alex/WebKit/WebKitBuild/Release/lib -o QtLauncher main.o -L/usr/local/lib -L/usr/home/alex/WebKit/WebKitBuild/Release/lib -lWebKitQt -lQtGui -L/usr/ports/x11-toolkits/qt4-gui/work/qt-x11-opensource-src-4.2.2/lib -L/usr/local/lib -L/usr/X11R6/lib -lpng -L/usr/ports/devel/qt4-corelib/work/qt-x11-opensource-src-4.2.2/lib -lXi -lXrender -lXrandr -lXfixes -lXcursor -lXinerama -lfreetype -lfontconfig -lXext -lX11 -lQtCore -lz -lm -lglib-2.0 -liconv /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderObject::repaintObjectsBeforeLayout()' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderFlexibleBox::calcMinMaxWidth()' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderImage::calcMinMaxWidth()' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderBlock::repaintObjectsBeforeLayout()' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderText::calcMinMaxWidth()' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderInline::calcMinMaxWidth()' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderReplaced::calcMinMaxWidth()' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderContainer::insertChildNode(WebCore::RenderObject*, WebCore::RenderObject*)' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderObject::appendChildNode(WebCore::RenderObject*)' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderObject::removeChildNode(WebCore::RenderObject*)' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderBlock::isPointInScrollbar(WebCore::HitTestResult&, int, int, int, int)' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderContainer::removeChildNode(WebCore::RenderObject*)' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderContainer::appendChildNode(WebCore::RenderObject*)' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderObject::insertChildNode(WebCore::RenderObject*, WebCore::RenderObject*)' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderObject::updateFirstLetter()' /usr/home/alex/WebKit/WebKitBuild/Release/lib/libWebKitQt.so: undefined reference to `WebCore::RenderBlock::calcMinMaxWidth()' gmake[1]: *** [QtLauncher] Error 1 gmake[1]: Leaving directory `/usr/home/alex/WebKit/WebKitBuild/Release/WebKitQt/QtLauncher' gmake: *** [sub-WebKitQt_QtLauncher-make_default-ordered] Error 2
Attachments
Mark Rowe (bdash)
Comment 1 2007-04-27 03:12:04 PDT
As a workaround you can define the WEBKIT_FULLBUILD environment variable before running build-webkit. This will force a clean build.
luying.pan
Comment 2 2009-10-15 12:32:29 PDT
I've seen the same thing. I'm having trouble rebuilding the qtlauncher. I don't want to do a clean build if all I changed was the qt launcher. Deleting the main.o for the QtLauncher didn't even solve that one.
Martin Robinson
Comment 3 2021-02-05 00:22:56 PST
Closing this since the Qt port is not part of the tree any longer.
Note You need to log in before you can comment on or make changes to this bug.