Bug 30399

Summary: [bsd.cpu.mk] [patch] Have Fortran use the CPUTYPE variable
Product: Base System Reporter: gjohnson <gjohnson>
Component: confAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description gjohnson 2001-09-06 17:00:03 UTC
        Programs compiled with Fortran do not make use of the CPUTYPE
        variable.  The enclosed patch allows Fortran programs to be
        compiled with a machine optimization setting via the CPUTYPE
        variable.

Fix: Apply the enclosed patch to src/share/mk/bsd.cpu.mk
Comment 1 Robert Watson freebsd_committer freebsd_triage 2008-01-25 16:30:06 UTC
Responsible Changed
From-To: freebsd-bugs->brueffer

Assign to brueffer who has recently been cleaning up Fortran-related 
issues.  Since Fortran is no longer in the base system (now just a 
port), this may be OBE.
Comment 2 b. f. 2010-09-21 10:28:54 UTC
>Assign to brueffer who has recently been cleaning up Fortran-related
>issues. Since Fortran is no longer in the base system (now just a
>port), this may be OBE.

I don't know if this cleanup effort was abandoned, considering the
amount of time that has passed since the above comment, but just for
the record: if all Fortran-related material in the base system
makefiles is removed without accompanying changes to FreeBSD Ports, it
will break many of the Fortran-related ports, as many of these ports
use bsd.lib.mk, etc.  If a removal is still planned, the Fortran bits
should be extracted and moved to ports/Mk/bsd.gcc.mk, or another
relevant ports makefile.

b.
Comment 3 Christian Brueffer freebsd_committer freebsd_triage 2011-09-11 21:37:56 UTC
Responsible Changed
From-To: brueffer->freebsd-bugs

I haven't used Fortran in a long time.
Comment 4 Alexander Best freebsd_committer freebsd_triage 2011-11-21 23:24:45 UTC
State Changed
From-To: open->feedback

I suggest we close this problem report. Fortran now is simply *some* programming 
language in ports, after its removal from base. It shouldn't be handled 
any differently than any other /usr/ports/lang/*, imo. 
Thus it should not be dealt with in bsd.cpu.mk. 

Thoughts?
Comment 5 Eitan Adler freebsd_committer freebsd_triage 2012-01-14 15:46:36 UTC
State Changed
From-To: feedback->closed

per arundel