While pondering various upgrade strategies, I want to make sure I'm clear on exactly what the issues are. Say I've got libfoo and libbar, both C++ libs, where libbar links to libfoo. And I've got libquxx, a plain C lib, where libqux links to libbar but not directly to libfoo. And everything is built with gcc-3.3. For example:
g++-3.3 -dynamiclib foo.cc -o libfoo.dylib g++-3.3 -dynamiclib bar.cc -o libbar.dylib -lfoo gcc-3.3 -dynamiclib qux.c -o libqux.dylib -lbar If I rebuild foo using gcc-4.0, I have to rebuild bar, since the C++ ABI has changed: libfoo.dylib compiled with different ABI are not binary-compatible. Because I rebuild bar, do I have to rebuild biz, or does the ABI incompatibility issue only affect the C++ (not "pure C") interface? dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
