Martin Costabel <[EMAIL PROTECTED]> wrote:

> 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.

I get it, thank you.

Looking into the log, I see that uic reports many errors like this:

  uic: cannot load image file images/designer_adjustsize.png
  uic: cannot load image file images/designer_edithlayoutsplit.png
  uic: cannot load image file images/designer_left.png
  uic: cannot load image file images/designer_sizeall.png

In fact there are about as many errors as there are png images in the
images subdirectory.  The images are there, though, and look fine in a
browser.  They all are readable by their owner (who is root, who is also
doing the build).

The compile of qmake_image_collection.cpp is immediately following these
error messages, but it isn't obviously marred by any error messages of
its own.

I tested uic on a simpler case, but it won't work with only one
perfectly acceptable png.  (Gives the same error.)  In order to do this,
I had to copy the libqt-mt.3.dylib under fink.build into /sw/lib, since
uic wasn't finding any qt library on its own.

The error is apparently issued by a failure in QImage::load, which I
have no idea how to find.  But I did notice that the linking of
libqt-mt.3.dylib had a bunch of warnings:

  ld: warning -dylib_install_name /sw/lib/libqt-mt.3.dylib not found in segment 
address table LD_SEG_ADDR_TABLE /sw/var/lib/fink/prebound/seg_addr_table
  ld: warning -prebind ignored because MACOSX_DEPLOYMENT_TARGET environment 
variable greater or equal to 10.4
  ld: warning multiple definitions of symbol _glPointParameteri
  
/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib(gll_api.o)
 definition of _glPointParameteri
  /usr/X11R6/lib/libGL.dylib(dri_dispatch.o) definition of _glPointParameteri
  ld: warning multiple definitions of symbol _glPointParameteriv
  
/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib(gll_api.o)
 definition of _glPointParameteriv
  /usr/X11R6/lib/libGL.dylib(dri_dispatch.o) definition of _glPointParameteriv
  ld: warning multiple definitions of symbol _dladdr
  /sw/lib/libdl.dylib(dlfcn.o) definition of _dladdr
  /usr/lib/libm.dylib(dyldAPIsInLibSystem.o) definition of _dladdr
  ld: warning multiple definitions of symbol _dlclose
  /sw/lib/libdl.dylib(dlfcn.o) definition of _dlclose
  /usr/lib/libm.dylib(dyldAPIsInLibSystem.o) definition of _dlclose
  ld: warning multiple definitions of symbol _dlerror
  /sw/lib/libdl.dylib(dlfcn.o) definition of _dlerror
  /usr/lib/libm.dylib(dyldAPIsInLibSystem.o) definition of _dlerror
  ld: warning multiple definitions of symbol _dlopen
  /sw/lib/libdl.dylib(dlfcn.o) definition of _dlopen
  /usr/lib/libm.dylib(dyldAPIsInLibSystem.o) definition of _dlopen
  ld: warning multiple definitions of symbol _dlsym
  /sw/lib/libdl.dylib(dlfcn.o) definition of _dlsym
  /usr/lib/libm.dylib(dyldAPIsInLibSystem.o) definition of _dlsym
  ln -s libqt-mt.3.3.4.dylib libqt-mt.dylib
  ln -s libqt-mt.3.3.4.dylib libqt-mt.3.dylib
  ln -s libqt-mt.3.3.4.dylib libqt-mt.3.3.dylib
  /bin/rm -f ../lib/libqt-mt.3.3.4.dylib
  /bin/rm -f ../lib/libqt-mt.dylib
  /bin/rm -f ../lib/libqt-mt.3.dylib
  /bin/rm -f ../lib/libqt-mt.3.3.dylib
  /bin/mv -f libqt-mt.3.3.4.dylib libqt-mt.dylib libqt-mt.3.dylib 
libqt-mt.3.3.dylib ../lib/

Do you think any of these look culpable?  I tried tracking down the
QImage code, but I've kind of run up against my c++ limitations (that
is, I got lost).

Does any of this provide a useful clue?  I'm certainly grateful for your
help so far.

 -tom

-- 
 ------------------------
 tomfool at as220 dot org
 http://sgouros.com  
 http://whatcheer.net


-------------------------------------------------------
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
Fink-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to