| 1 |
Hi all, |
| 2 |
|
| 3 |
GCC 4.1 will be unmasked this week. A major consequence for scientific |
| 4 |
users is the switch from g77 to gfortran. |
| 5 |
|
| 6 |
Things you can do to help make the switch easier for everyone: |
| 7 |
|
| 8 |
Developers: Check all your Fortran packages to ensure they work with |
| 9 |
gfortran from sys-devel/gcc-4.1.1_pre20060517. If they're C/C++, it's |
| 10 |
also worth testing your packages because GCC 4 is tougher on compliance |
| 11 |
than GCC 3. |
| 12 |
|
| 13 |
Users/Testers: Unmask and install GCC 4.1 with `echo |
| 14 |
"=sys-devel/gcc-4.1*" >> /etc/portage/package.unmask` and `emerge gcc`. |
| 15 |
Switch to it with gcc-config (Use `gcc-config -l` to list available |
| 16 |
compilers). Install portage-utils and run `emerge --oneshot $(qlist -I |
| 17 |
-C sci*/)`. This will reinstall all your sci-* packages using your new gcc. |
| 18 |
|
| 19 |
|
| 20 |
When you come across a broken package, file a bug for it. |
| 21 |
|
| 22 |
Packages I know don't work: |
| 23 |
{blas,cblas,lapack}-reference -- I have patches for these |
| 24 |
apbs |
| 25 |
numarray |
| 26 |
|
| 27 |
Thanks, |
| 28 |
Donnie |
| 29 |
|
| 30 |
1. http://www.gentoo.org/news/en/gwn/20060522-newsletter.xml#doc_chap1 |
Archives