From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1FjpkG-0004eu-DO for garchives@archives.gentoo.org; Sat, 27 May 2006 03:45:44 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.6) with SMTP id k4R3isNA009952; Sat, 27 May 2006 03:44:54 GMT Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.200.81]) by robin.gentoo.org (8.13.6/8.13.6) with ESMTP id k4R3irRk025389 for ; Sat, 27 May 2006 03:44:54 GMT Received: from [24.21.55.62] (c-24-21-55-62.hsd1.or.comcast.net[24.21.55.62]) by comcast.net (sccrmhc11) with ESMTP id <2006052703445201100c376ie>; Sat, 27 May 2006 03:44:52 +0000 Message-ID: <4477CB2D.2020902@cesmail.net> Date: Fri, 26 May 2006 20:44:45 -0700 From: "M. Edward (Ed) Borasky" User-Agent: Thunderbird 1.5.0.2 (X11/20060430) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-science@gentoo.org Reply-to: gentoo-science@lists.gentoo.org MIME-Version: 1.0 To: gentoo-science@lists.gentoo.org Subject: Re: [gentoo-science] Testing with GCC 4 References: <447332A3.9030802@gentoo.org> In-Reply-To: <447332A3.9030802@gentoo.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 38b4966c-15b3-4197-bbb4-4e9e30991431 X-Archives-Hash: c1c86dc8973ba1d81fa3f3d64ce22e8c By a strange coincidence, I'm beta testing R 2.3.1 this weekend. I have a "corner case" that usually fails -- use lapack-atlas on an Athlon Tbird and run "make check-all" in R. Of course, the R folks won't accept a bug because they deprecate use of external Lapack in general. Anyhow, I might as well throw gcc 4.1 into the mix. Do I need to do anything special with the libraries? Donnie Berkholz wrote: > Hi all, > > GCC 4.1 will be unmasked this week. A major consequence for scientific > users is the switch from g77 to gfortran. > > Things you can do to help make the switch easier for everyone: > > Developers: Check all your Fortran packages to ensure they work with > gfortran from sys-devel/gcc-4.1.1_pre20060517. If they're C/C++, it's > also worth testing your packages because GCC 4 is tougher on compliance > than GCC 3. > > Users/Testers: Unmask and install GCC 4.1 with `echo > "=sys-devel/gcc-4.1*" >> /etc/portage/package.unmask` and `emerge gcc`. > Switch to it with gcc-config (Use `gcc-config -l` to list available > compilers). Install portage-utils and run `emerge --oneshot $(qlist -I > -C sci*/)`. This will reinstall all your sci-* packages using your new gcc. > > > When you come across a broken package, file a bug for it. > > Packages I know don't work: > {blas,cblas,lapack}-reference -- I have patches for these > apbs > numarray > > Thanks, > Donnie > > 1. http://www.gentoo.org/news/en/gwn/20060522-newsletter.xml#doc_chap1 > > -- M. Edward (Ed) Borasky http://linuxcapacityplanning.com -- gentoo-science@gentoo.org mailing list