Summary: | gcc 4.3.3 does not build g77 or gfortran | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | D J Capelis <dev> |
Component: | [OLD] GCC Porting | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
D J Capelis
2009-02-22 07:21:57 UTC
To clarify, there is a gfortran binary that is built and installed, it's just named gfortran-4.3.3 instead of gfortran. Packages expecting g77 will probably break even if this is properly named gfortran. (That said, I've symlinked this binary to g77 on my machine and it's working well enough to compile the fortran programs I've encountered in the tree so far...) Well, from: 1. equery f =sys-devel/gcc-4.1.2: /usr/bin /usr/bin/c++-4.1.2 /usr/bin/cpp-4.1.2 /usr/bin/g++-4.1.2 /usr/bin/gcc-4.1.2 /usr/bin/gfortran-4.1.2 2. equery f =sys-devel/gcc-4.3.3: /usr/bin /usr/bin/c++-4.3.3 /usr/bin/cpp-4.3.3 /usr/bin/g++-4.3.3 /usr/bin/gcc-4.3.3 /usr/bin/gfortran-4.3.3 So this bug is probably invalid. Perhaps, something gone wrong during gcc-config ? Yes, this is the case. A good round of gcc-config appears to have fixed this. Oops. Apologies, closing as invalid. |