*** For details on how to be removed from this list visit the *** *** CCP4 home page http://www.ccp4.ac.uk ***
Harry, the 'write internal' bug in gfortran 4.1 is fixed in 4.2. Also AFAIK g95 (all versions) don't suffer from this bug (though of course there may well be different bugs!). -- Ian > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Harry Powell > Sent: 05 January 2006 14:38 > To: [email protected] > Subject: Re: [ccp4bb]: ccp4 v6.0 on Fedora core4 > > *** For details on how to be removed from this list visit the *** > *** CCP4 home page http://www.ccp4.ac.uk *** > > > Hi > > I'd just like to concur with Bill on that - there are > problems with gfortran that break the mosflm build - I > haven't yet managed to get a working copy of mosflm using > gfortran (though I haven't tried for a couple of months). g77 > seems to work fine and is what I use and recommend. > > > > Maybe the developers could comment on whether there is _any_ > > > programm in > > > ccp4-5.99.5 which does not compile with g77 (and if not, why they > > > chose gfortran as standard fortran compiler rather than > the - I dare > > > say established - g77)? > > > > I'm not a developer, but I messed around a bit with gfortran on the > > latest debian (ubuntu). > > > > Mosflm compiles but is completely broken by gfortran. > Using the CCP4 > > patch, I found that CCP4 compiles out of the box with > gfortran, gcc4 > > and g++4. (I found that I had to have CCP4 build its own version of > > fftw for clipper to compile). I ran the unix runnable examples. It > > hangs on findncs.exam. watertidy-3shells failed. The > > g77 version I compiled passes all the tests. Here's the log file. > > > > > > http://xanana.ucsc.edu/linux/logs/run_all.log > > > > Bill > > > > PS: As you found, g77-3.4 works just great with gcc-4.x > > > > > > Harry > -- > Dr Harry Powell, MRC Laboratory of Molecular Biology, MRC > Centre, Hills Road, Cambridge, CB2 2QH > > > > Disclaimer This communication is confidential and may contain privileged information intended solely for the named addressee(s). It may not be used or disclosed except for the purpose for which it has been sent. If you are not the intended recipient you must not review, use, disclose, copy, distribute or take any action in reliance upon it. If you have received this communication in error, please notify Astex Therapeutics Ltd by emailing [EMAIL PROTECTED] and destroy all copies of the message and any attached documents. Astex Therapeutics Ltd monitors, controls and protects all its messaging traffic in compliance with its corporate email policy. The Company accepts no liability or responsibility for any onward transmission or use of emails and attachments having left the Astex Therapeutics domain. Unless expressly stated, opinions in this message are those of the individual sender and not of Astex Therapeutics Ltd. The recipient should check this email and any attachments for the presence of computer viruses. Astex Therapeutics Ltd accepts no liability for damage caused by any virus transmitted by this email. E-mail is susceptible to data corruption, interception, unauthorized amendment, and tampering, Astex Therapeutics Ltd only send and receive e-mails on the basis that the Company is not liable for any such alteration or any consequences thereof.
