-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Daniel Macks wrote: | 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?
If your app/library does not use any c++ api then it does not need to be rebuilt. You can use Ben's idea to check this. nm -g app > out1; nm -g app | c++filt > out2; cmp out1 out2 If they differ then the app needs to be rebuilt. Peter - -- Peter O'Gorman - http://www.pogma.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Darwin) iQCVAwUBQsB8oLiDAg3OZTLPAQINWQP/WaWC2PJvRJ/8p/r/n1tbeMwe8CKPvG1X aHTKkRNS4e1YlwgZvErcVWG4qKdQnV0T8Qt1w5aexw+2g44JGkOqu8ge8ektaFxO wU05N27ydNNg15iXpJnvka/zsJmXEc4aqzWhMAu3K1qkcgOHbujwYEJwEnuaFgM6 4T5tDADZp1I= =yyMc -----END PGP SIGNATURE----- ------------------------------------------------------- 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
