David Reiser wrote:
[]
Making all in widgets
/sw/bin/uic qbprogress.ui -impl qbprogress.ui.h -o qbprogress.ui.cpp
dyld: Symbol not found: __cg_jpeg_resync_to_restart
Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
  Expected in: /sw/lib/libJPEG.dylib

Do you have DYLD_LIBRAY_PATH set to /sw/lib? Don't do this. The ImageIO library is linked to /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib which Tiger's new improved dynamic linker dyld loves to mix up with /sw/lib/libjpeg.dylib, although the latter has a completely different install_name.

I can play with the symlink to get /sw/lib/libJPEG.dylib to point back

It is easier to remove the libjpeg package. If you change the symlink and then try to build anything that links to Fink's libjpeg, you will get unpleasant surprises.

into /System/...../ImageIO/libJPEG.dylib, but what the heck is uic doing over in /System? (If one takes out the 'cg' in that missing symbol name, the symbol is in the /sw/lib/libJPEG.dylib target.)

Well, uic uses X11 and is therefore linked to a couple of X11 libraries, and /usr/X11R6/lib/libfreetype.6.dylib is linked to the ApplicationServices framework, which in turn pulls in a bunch of other frameworks, from WebServicesCore to SpeechSynthesis. To see this, start uic, or for that matter any program that is linked to X11, even a simple xterm, with the DYLD_PRINT_LIBRRARIES environment variable set.

While I don't know all the details of the software build, I can almost guarantee that Qt is the only thing that has any clue that a Mac might be involved.

After I do the symlink shenanigans, the build continues, but I end up at:

g++ -I/opt/include -g -Wall -g -o .libs/aqofxconnect-qt3-wizard qt3_wizard.o -Wl,-bind_at_load -L/opt/lib ../libs/.libs/libqt3wizard.a -L/Users/dbr/desktop/aqbanking-1.6.1/src/libs/aqbanking -L/sw/lib -L/Users/dbr/desktop/aqbanking-1.6.1/src/frontends/qbanking /Users/dbr/desktop/aqbanking-1.6.1/src/frontends/qbanking/.libs/libqbanking.dylib -L/sw/lib/freetype219/lib -L/usr/X11R6/lib -L/Users/dbr/desktop/aqbanking-1.6.1/src/plugins/backends/aqofxconnect/plugin /opt/lib/libaqofxconnect.dylib /opt/lib/libaqbanking.dylib /opt/lib/libofx.dylib /sw/lib/libosp.dylib -lpthread -lstdc++ /opt/lib/libgwenhywfar.dylib /sw/lib/libintl.dylib /sw/lib/libiconv.dylib -lc -lssl -lcrypto /sw/lib/libqt-mt.dylib -lresolv -lz -lGL -lXmu -lXrender -lXrandr -lXcursor -lXinerama -lXft /sw/lib/freetype219/lib/libfreetype.dylib -lfontconfig -lXext -lX11 -lm -lSM -lICE -ldl
/usr/bin/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
/usr/bin/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
/usr/bin/ld: Undefined symbols:
typeinfo for QPtrCollection
typeinfo for QListViewItem
typeinfo for QListView
typeinfo for QDialog
typeinfo for QWidget
collect2: ld returned 1 exit status

and it looks like I have something amiss in my Qt setup somewhere else.

Yes. Qt is built using g++-3.3, just like the rest of (powerpc) MacOSX, and you are using g++-4.0 to compile your application. But g++-3.3 and g++-4.0 produce binary-incompatible object files which is what you are observing here.

As long as you link to the g++-3.3-built qt libraries, you need to build your application with g++-3.3, too. You can also try to rebuild qt3 with g++-4.0 and then cross your fingers that the binary incompatibility with the system libGL and libGLU (which were compiled with g++-3.3) doesn't bite you later on.

This software does build and run on Linux.

Usually, when a linux distribution changes compilers to a binary incompatible new version, it requires you to reinstall the whole distribution, system, glibc, applications and all. Fink tries to find an upgrade path (more like a tightrope for which it is unknown whether it is really attached to the other side :-) ) from a gcc-3.3 based system to applications built with gcc-4.0. This is why we currently have the "10.4-transitional" tree which builds everything C++ with g++-3.3. In the final "10.4" tree, we will have many things built with g++-4.0, but it is open when this will see the light of day.

--
Martin





-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to