Just to clarify this issue with gcc in more detail. While those gcc releases which don't recognize darwin10 could be run on darwin10 as prebuilt binaries, the compiler itself would be miscompiled under darwin10 (so you can't build the package itself but could run a copy built under darwin9). The first full multilib build of x86_64-apple-darwin9/10 is available in gcc44. The gcc43 package could in theory be built under darwin9 as a x86_64-apple-darwin9 target but it wouldn't have an i386 multilib. So again, the best approach is to not allow any gcc older than gcc44 to be built on 10.6 and get serious about fixing the remaining packages that need adjusted to build on gcc 4.4.0. Most code should have patches available either from Fedora Rawhide or Debian that packagers can use. Jack
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel