It's probably worth thinking about a policy for what to do about packages that don't build under XCode 2.2/gcc4.0.1 due to "nested functions" errors. As Martin has pointed out, other than in a few simple cases of bad coding, these are nontrivial to patch out. And it will take time for upstream developers to make the changes (if they bother at all).
A couple of options spring to my mind: 1) Since we've already suggested that people not update, we go ahead and commit such packages as long as they build with gcc4.0.0. This has the virtue that we hopefully won't have to make too many changes if Apple releases an update to allow nested functions again. 1A) For longer-term usage, we'd need a virtual package that marks gcc4.0.1 from XCode2.2 (current) as bad, and have all packages with nested functions BuildConflict on that. 2) We bite the bullet and use gcc3.3 to build all of the packages that are found not to build due to these errors and that don't require gcc4 to build. For those that do require gcc4 to build, I guess it's back to 1). -- Alexander K. Hansen Fink Documenter [Day Job] Levitated Dipole Experiment http://psfcwww2.psfc.mit.edu/ldx/ ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28&alloc_id845&op=click _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
