NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

toolchain/41220: gfortran is not in the compiler set

>Number:         41220
>Category:       toolchain
>Synopsis:       gfortranis not in the compiler set
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    toolchain-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 15 13:00:01 +0000 2009
>Release:        NetBSD 5.0_RC3
System: NetBSD slashing 5.0_RC3 NetBSD 5.0_RC3 (SLASHING) #0: Tue Apr 14 
00:34:13 EDT 2009 
root@slashing:/usr/cvs/obj.i386/sys/arch/i386/compile/SLASHING i386
Architecture: i386
Machine: i386

Many releases ago we had g77 as part of the compiler set.  Then g77 was
removed from the gcc distribution and we dropped g77.  Now gfortran
is in the gcc distribution.  Since f2c does not support f90/f95 constructs
we end up needing to build gfortran in pkgsrc to have a semi-modern
fortran compiler.  I'm wondering if it would be easier to maintain a working
fortran if we built it from the same gcc version as what is in base so we
can more easily take advantage of any patches we have.

try to compile f90 or f95 numerical libraries, realize we have no fortran
compiler.  Install f2c from pkgsrc, realize it is a f77 compiler.  Download
and compile a recent gcc that includes gfortran, worry about incompatibilities
and conflicts between that and the gcc in the base system which was used
to compile lots of other stuff.


Is this is simple as setting a config option and updating a set list?



Home | Main Index | Thread Index | Old Index