Chris Zubrzycki wrote:
[]
> Well, if it is a c-only app, no, it does not need to be rebuilt. If it 
> uses c++, then it needs to be rebuilt, or else it will not work. gcc3 
> breaks c++ binary compatibility because it now conforms (almost) to the 
> ISO C++ standard. Version 3.2, afaik, will have full compatibility, and 
> hopefully from then on nothing will break like this again. We have most 
> packages working under Jaguar/gcc3, but not all. If you know c++, we can 
> always use more help :-)
> 
> PS: is it possible to continue using gcc2 under 10.2, but the problem is 
> that most things built under 10.2 will use gcc3, and gcc2 c++ programs 
> cannot link to gcc3 libraries, and vice versa.

Could someone in the know (Chris?) please describe this more precisely, 
in particular I would like to know:

1. Is *everything* compiled with c++ under one version incompatible with 
everything compiled under the other version? Or is this incompatibility 
restricted to objects linked with special headers or libraries?

2. What are the symptoms of something breaking because of such an 
incompatibility? Do the binaries or dyld or someone else give a 
comprehensible error message, or do they just silently die or eat the 
filesystem or what?

3. How can I see whether a dylib compiled with gcc2 will be compatible 
with binaries compiled with gcc3 or not? Is there some characteristic 
information coded in somewhere?

If this breakage is indeed widespread (I haven't seen it yet although I 
have occasionally built fink packages with gcc-3.1 and then forgot about 
them), the answers to these questions will be important for answering 
the FAQs that will probably be asked.

-- 
Martin





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to