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
--
[email protected] mailing list
