tom sgouros wrote: []
No /lib on this system, but I also looked in /usr/local/lib, with the same negative result. What is the theory behind thinking that having a bad library would cause an "undefined symbol" error? I'm not sure I get that. Is the idea that some early stage of the compile would find that symbol and therefore not include it in some library?
This is somewhat complicated: The missing symbol qInitImages_designercore is normally defined in the file tools/designer/designer/qmake_image_collection.cpp. This file is not contained in the source tarball, but is created during compile time. The creation of this file fails in your case, and therefore the symbol is undefined.
Look in your build logs for qmake_image_collection.cpp and try to find out why it was not built. The file is built using the newly compiled "uic" executable which is linked to some qt library, and if this library exists in /sw/lib, but with a wrong version, uic can fail. This is the mechanism by which an existing older installation of qt3 can produce the error you are seeing. Of course, uic can fail for some other reason, but it is hard to make a guess from the distance.
-- Martin ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
