Gentoo Archives: gentoo-science

From: "M. Edward (Ed) Borasky" <znmeb@×××××××.net>
To: gentoo-science@l.g.o
Subject: Re: [gentoo-science] Testing with GCC 4
Date: Sun, 28 May 2006 05:31:20
Message-Id: 4479353D.6080405@cesmail.net
In Reply to: Re: [gentoo-science] Testing with GCC 4 by "M. Edward (Ed) Borasky"
1 Good news! R-2.3.1 beta compiled and installed successfully with both
2 3.4.5 and 4.1.1!! I also recompiled most of the library packages. I
3 haven't seen any failures that would have been compiler-related, so I'm
4 tempted to leave gcc 4.1.1 as the default for a while.
5
6 I don't have much more Fortran-based software, but I do think it's worth
7 recompiling blas-atlas and lapack-atlas with gcc 4.1.1.
8
9 M. Edward (Ed) Borasky wrote:
10 > By a strange coincidence, I'm beta testing R 2.3.1 this weekend. I have
11 > a "corner case" that usually fails -- use lapack-atlas on an Athlon
12 > Tbird and run "make check-all" in R. Of course, the R folks won't accept
13 > a bug because they deprecate use of external Lapack in general. Anyhow,
14 > I might as well throw gcc 4.1 into the mix. Do I need to do anything
15 > special with the libraries?
16 >
17 >
18 >
19 > Donnie Berkholz wrote:
20 >
21 >> Hi all,
22 >>
23 >> GCC 4.1 will be unmasked this week. A major consequence for scientific
24 >> users is the switch from g77 to gfortran.
25 >>
26 >> Things you can do to help make the switch easier for everyone:
27 >>
28 >> Developers: Check all your Fortran packages to ensure they work with
29 >> gfortran from sys-devel/gcc-4.1.1_pre20060517. If they're C/C++, it's
30 >> also worth testing your packages because GCC 4 is tougher on compliance
31 >> than GCC 3.
32 >>
33 >> Users/Testers: Unmask and install GCC 4.1 with `echo
34 >> "=sys-devel/gcc-4.1*" >> /etc/portage/package.unmask` and `emerge gcc`.
35 >> Switch to it with gcc-config (Use `gcc-config -l` to list available
36 >> compilers). Install portage-utils and run `emerge --oneshot $(qlist -I
37 >> -C sci*/)`. This will reinstall all your sci-* packages using your new gcc.
38 >>
39 >>
40 >> When you come across a broken package, file a bug for it.
41 >>
42 >> Packages I know don't work:
43 >> {blas,cblas,lapack}-reference -- I have patches for these
44 >> apbs
45 >> numarray
46 >>
47 >> Thanks,
48 >> Donnie
49 >>
50 >> 1. http://www.gentoo.org/news/en/gwn/20060522-newsletter.xml#doc_chap1
51 >>
52 >>
53 >>
54 >
55 >
56
57 --
58 M. Edward (Ed) Borasky
59
60 http://linuxcapacityplanning.com
61
62 --
63 gentoo-science@g.o mailing list