[Fink-devel] GCC field

[David R. Morrison]

We introduced that GCC field into fink some time back due to the ABI 
incompatibilities between different versions of gcc, when the code in 
question was C++ code.  The GCC field provided a mechanism for fink 
developers to track which packages had compiled code which was 
restricted to a particular ABI.

I believe that this is still useful information for fink to track, but 
that calling it GCC is misleading.  We will soon be getting a post-3.3 
version of gcc from Apple, but there is no ABI change for versions 
after 3.3.  Thus, it will be perfectly appropriate to compile a package 
labeled "GCC: 3.3" with gcc 3.4 or later.

I thus propose to rename the GCC field, calling it GCC-ABI instead.  If 
there are no objections to this, it can be accomplished be a mass edit 
to our package database (as has been done a few times before).  There 
is one place in the fink code where the GCC field is tested, but that 
test can easily be rewritten.

I believe that it will cause much less confusion in the future if the 
package says "GCC-ABI: 3.3" and the docs explain that the ABI for GCC 
stablilzed at 3.3.

Thoughts?
  -- Dave

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel