| 1 |
On Sun, 18 Jun 2006 02:57:29 +0400 |
| 2 |
Samir Mishra <sqmishra@×××.ae> wrote: |
| 3 |
|
| 4 |
> Ramin.T wrote: |
| 5 |
> > alain.didierjean@××××.fr wrote: |
| 6 |
> > |
| 7 |
> >> Just finished recompiling the whole world (emerge -eav world). One |
| 8 |
> >> of the few packages that would fail (7 out of =- 720) is fftw. The |
| 9 |
> >> reason is obvious : no fortran compiler installed. |
| 10 |
> >> Problem : I couldn't find the proper package to emerge so I have a |
| 11 |
> >> 4.1.1 fortran compiler for my amd64 computer. |
| 12 |
> >> Please help... |
| 13 |
> >> |
| 14 |
> >> -- |
| 15 |
> >> ~adj~ |
| 16 |
> >> |
| 17 |
> >> |
| 18 |
> >> |
| 19 |
> > I think only the name changed ... |
| 20 |
> > it is not g77 anymore but gfortran. |
| 21 |
> > |
| 22 |
> > They will probably only have to change the ebuild |
| 23 |
> > |
| 24 |
> > Regards |
| 25 |
> > Ramin |
| 26 |
> > |
| 27 |
> I created a link from gfortran to g77 in the appropriate directories. |
| 28 |
> This seems to work for me. |
| 29 |
|
| 30 |
Do be careful with that - this from Donnie Berkholz' blog: |
| 31 |
|
| 32 |
http://spyderous.livejournal.com/76320.html |
| 33 |
|
| 34 |
"The entrance of GCC 4.1 into testing has made a lot possible, but also |
| 35 |
requires a lot of fixing. This is particularly the case in scientific |
| 36 |
computing, where there's an entirely new Fortran compiler -- gfortran. |
| 37 |
Please note that gfortran is NOT a renamed g77. It accepts different |
| 38 |
options, and it compiles different code. Only gfortran will compile |
| 39 |
Fortran90 and Fortran95 code. Only g77 will accept common options such |
| 40 |
as -fno-globals. Do not assume they are the same." |
| 41 |
|
| 42 |
-- |
| 43 |
Kevin F. Quinn |
Archives