On Fri, Oct 21, 2011 at 09:01:58AM -0700, David R. Morrison wrote: > > On Oct 21, 2011, at 8:50 AM, Jack Howarth wrote: > > > On Fri, Oct 21, 2011 at 08:05:38AM -0700, David R. Morrison wrote: > >> So at the very least, we should put a news item on the fink webpage > >> warning users that fink on 10.6 is currently incompatible with Xcode 4.2, > >> and suggesting a downgrade to Xcode 3.2.6. > >> > >> Another short-term measure would be to put a test into fink to check for > >> Xcode 4.2 on 10.6, and warn users that they should downgrade. > >> > >> The question of how and whether to adapt the fink 10.6 release to > >> accomodate this major change by apple is a more difficult one, and will > >> require additional thought as well as time to implement. > >> > >> -- Dave > > > > Dave, > > The change as implemented on > > http://sourceforge.net/tracker/?func=detail&aid=3426897&group_id=17203&atid=317203 > > will be transparent to current Fink users who aren't on 10.6 with Xcode > > 4.2. The only change for Lion users will be > > that the clang compiler wrappers will explictly pass the --arch x86_64 > > (which again should be a transparent change > > and cause no issues). > > I been able to build... > > > Lots of questions here, including: > 1) Do things build differently? One of our main design principles in fink is > that things should build the same for everybody.
I don't quite understand that question. Yes, we are switching the fink system compiler under SL Xcode 4.2 from llvm-gcc to clang. However, the only alternative would be create a new path-prefix-gcc42 and force fink, under SL Xcode 4.2, to use gcc-4.2 instead. > 2) Any problem with mixing and matching, i.e., upgrading the compiler on an > already-installed fink? There really shouldn't be an issue with that. If any are found, they should be considered Xcode bugs and radar reports opened against them. I should expand on my main interest here. While clang is being tested well on fink 10.7 at x86_64, very little testing occurs for i386 code generation under the clang compilers. Fink supporting path-prefix-clang under SL Xcode 4.2 achieves the goal of unbreaking fink on the configuration while also providing a test bed for discovering clang bugs in i386 code generation with GPLv3 software which Apple can't compile. Recent events have proved the value of such a test bed. For example, David Fang recently reported breakage in libmpfr4-3.1.0 when built with clang from Lion Xcode 4.2. This turned out to be a previously unknown bug in darwin's new tls support which is now enabled in the clang compiler under Xcode 4.2... http://llvm.org/bugs/show_bug.cgi?id=11111 I was able to use fink to generate a standalone test case for rader which allowed Apple to rapidly fix the issue for the LLVM 3.0 release. Hopefully we will find similar issues under i386 fink built with clang which can be addressed upstream. Jack ps We should also not forget that using clang under SL Xcode 4.2 significantly shortens the average package build time and should be view as another bonus. > > -- Dave > ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
