Re: [Fink-devel] gfortran package
Still one has to ask exactly which compilers in the gcc4 package we should be focusing on? The gfortran compiler specifically is making really good progress. With patches to be added today, it should pass almost all of the NIST Fortran validation testsuite. I think we would be far better off doing the same thing for gfortran as we do for g95. Sampling the source code at regular intervals. Since gcc 4.1 is into stage 3, it is probably worthwhile testing that branch for gfortran since most of the new features and fixes go into that branch first. Better to help provide feedback now rather than to have to wait for the 4.1.1 release. Jack --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] gfortran package
On 28 Jul 2005, at 17:18, David R. Morrison wrote: Also, there is some danger of confusion between the "gcc4" which is a virtual package that the system provides, designed to insure that users have the correct Apple gcc package installed, and the gcc4 package... The virtual pkg is gcc4.0 JF --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] gfortran package
On Jul 26, 2005, at 12:43 AM, Jack Howarth wrote: Peter, You may have point regarding the 4.1 branch, but I would say that the 4.0.2 branch is highly unlikely to be much less stable for gfortran than the 4.0.1 release is. Again the question really is what is the purpose of the gcc4 package? If it is primarily a release mechanism for gfortran, then it is debatable if that is the most stable release. For instance, I don't even see the dejagnu lines in the gcc4.info script so it is unclear how closely we are monitoring regressions in gfortran relative to the gcc-testresults mailing list. Jack I'm not completely clear on why we have a gcc4 package at all. From this discussion, it seems that it is *not* because of other compilers (since those are in separate packages)? Also, there is some danger of confusion between the "gcc4" which is a virtual package that the system provides, designed to insure that users have the correct Apple gcc package installed, and the gcc4 package... -- Dave --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Giving up on ghc
Good morning. I have a version of ghc in my experimental that works for me on Panther. http://cvs.sourceforge.net/viewcvs.py/fink/experimental/crhalpin/ I don't have access to a tiger box, so I can't test it there. If I could get someone else to verify that it works for them on panther, I'll push it to unstable. To do this verification, - download ghc.info, ghc.patch, darcs.info, darcs.patch and put them in your /sw/fink/dists/local/main/finkinfo - fink install ghc 2>&1 | tee ghc.log if this fails, please mail me the ghc.log - fink install darcs 2>&1 | tee darcs.log if this fails, please mail me darcs.log - if nothing fails, celebrate. :-) Then mail me to let me know. If it actually works unmodified on Tiger, that'd be -really- neat. But I don't think it will. regards, crh pgpZJVXPU49QT.pgp Description: PGP signature
