I propose adding a check for the bad build, checking only the file /usr/libexec/gcc/darwin/ppc/3.3/cc1plus which is the one Martin Costabel has identified as causing the problem. "Build 1666" is the bad one for this file.
RangerRick indicated on IRC that it would not be too hard to create a "broken-gcc" package in VirtPackages.pm which shows up if the offending file has the offending build number. We could then test for this elsewhere in the code; for example, any time you are going to build or rebuild something with fink, you might receive a warning about a bad build of g++-3.3 if this broken-gcc package is present.
Or, maybe someone else would like to suggest a different place to insert this?
-- Dave
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
