thanks Michael, that indeed is the other good reason. It's actually the primary reason.
Andrew Am 05 Apr 2010 um 5:42 PM schrieb Michael Rapson: > Hi all, > > In my rather brief experience of getting deal.II set up on my laptop > under OS X (I now dual boot with Ubuntu and run deal.II there mainly > because it uses less RAM) one of the frustrations that arose was that > Fortran compilers are not provided. This means that if mpi support for > PETSc or Trilinos is required then different compilers must be used. > That leaves the option of compiling gcc yourself or looking for a > compiled version available on the internet. I ended up compiling > myself to get a consistent set of compilers to use. > > So Fortran support for PETSc and Trilinos is one reason that the xcode > gcc may not be suitable. If I have followed this post correctly it > seems like casting problems might be another? > > Regards, > Michael > > On Mon, Apr 5, 2010 at 4:50 PM, Andrew McBride <[email protected]> > wrote: >> Hi Wolfgang >> >> mmm, good question. why spend all this time messing with compilers. Well >> originally, it was to fix the issue with casting that we dealt with in a >> previous series of mails. Thus, I switched to the HPC version of gcc, as >> suggested by Luca. I recall this being the only issue.Perhaps I've forgotten >> some other very good reason... >> >> That said, I've just reinstalled deal.ii using the standard apple xcode gcc >> (gcc version 4.2.1 (Apple Inc. build 5646) (dot 1)) and all works fine. So >> step-21, step-5,step-6 and various others are all good. So, now it's not >> obvious what advantage there is to using a non-standard gcc on the mac. >> >> But now I'm a little confused. Khalid was having problem with step-6. If I >> run step-6 with the standard mac gcc all is fine: >> .... >> Cycle 7: >> Number of active cells: 3860 >> Number of degrees of freedom: 18353 >> >> I presume Khalid is using osx 10.6 and the latest version of xcode. >> >> Regards >> Andrew >> >> Am 05 Apr 2010 um 2:43 PM schrieb Wolfgang Bangerth: >> >>> >>>> Wolfgang, you were correct. The problem lies in the latest gcc 4.5 >>>> version (4.5.0 20100107 (experimental) (GCC)) released by >>>> http://sourceforge.net/projects/hpc/. I took the code snippet you sent >>>> me and ran it on the numerous gcc compilers one seems to accumulate when >>>> one uses a mac. The results are shown below. To summarise: The following >>>> gcc versions work fine for compiling the code snippet: gcc version 4.2.1 >>>> (Apple Inc. build 5646) (dot 1) >>>> gcc version 4.3.3 (GCC) >>>> gcc version 4.5.0 20090910 (experimental) (GCC). >>>> But the latest 4.5 version from hpc fails, i.e. >>>> gcc version 4.5.0 20100107 (experimental) (GCC) >>>> fails. >>> >>> I've opened GCC bug 43648 for this: >>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43648 >>> >>> >>>> This mac related compiler issue is quite frustrating. >>> >>> I get the impression that mac os x is tied rather closely to a particular >>> version of gcc and that using a different version of gcc leads to all >>> sorts of problems. Does it work to just use the relevant version of xcode, >>> or what is the reason y'all are playing with different versions of gcc? >>> >>> Best >>> W. >>> >>> ------------------------------------------------------------------------- >>> Wolfgang Bangerth email: [email protected] >>> www: http://www.math.tamu.edu/~bangerth/ >>> >> >> _______________________________________________ >> dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii >> > _______________________________________________ > dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii _______________________________________________ dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii
