| 1 |
By a strange coincidence, I'm beta testing R 2.3.1 this weekend. I have |
| 2 |
a "corner case" that usually fails -- use lapack-atlas on an Athlon |
| 3 |
Tbird and run "make check-all" in R. Of course, the R folks won't accept |
| 4 |
a bug because they deprecate use of external Lapack in general. Anyhow, |
| 5 |
I might as well throw gcc 4.1 into the mix. Do I need to do anything |
| 6 |
special with the libraries? |
| 7 |
|
| 8 |
|
| 9 |
|
| 10 |
Donnie Berkholz wrote: |
| 11 |
> Hi all, |
| 12 |
> |
| 13 |
> GCC 4.1 will be unmasked this week. A major consequence for scientific |
| 14 |
> users is the switch from g77 to gfortran. |
| 15 |
> |
| 16 |
> Things you can do to help make the switch easier for everyone: |
| 17 |
> |
| 18 |
> Developers: Check all your Fortran packages to ensure they work with |
| 19 |
> gfortran from sys-devel/gcc-4.1.1_pre20060517. If they're C/C++, it's |
| 20 |
> also worth testing your packages because GCC 4 is tougher on compliance |
| 21 |
> than GCC 3. |
| 22 |
> |
| 23 |
> Users/Testers: Unmask and install GCC 4.1 with `echo |
| 24 |
> "=sys-devel/gcc-4.1*" >> /etc/portage/package.unmask` and `emerge gcc`. |
| 25 |
> Switch to it with gcc-config (Use `gcc-config -l` to list available |
| 26 |
> compilers). Install portage-utils and run `emerge --oneshot $(qlist -I |
| 27 |
> -C sci*/)`. This will reinstall all your sci-* packages using your new gcc. |
| 28 |
> |
| 29 |
> |
| 30 |
> When you come across a broken package, file a bug for it. |
| 31 |
> |
| 32 |
> Packages I know don't work: |
| 33 |
> {blas,cblas,lapack}-reference -- I have patches for these |
| 34 |
> apbs |
| 35 |
> numarray |
| 36 |
> |
| 37 |
> Thanks, |
| 38 |
> Donnie |
| 39 |
> |
| 40 |
> 1. http://www.gentoo.org/news/en/gwn/20060522-newsletter.xml#doc_chap1 |
| 41 |
> |
| 42 |
> |
| 43 |
|
| 44 |
-- |
| 45 |
M. Edward (Ed) Borasky |
| 46 |
|
| 47 |
http://linuxcapacityplanning.com |
| 48 |
|
| 49 |
-- |
| 50 |
gentoo-science@g.o mailing list |
Archives