lsb

Define directory for Fortran's .mod files

Bug #1331480 reported by Jeff Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lsb
In Progress
Medium
Unassigned
Mandriva
In Progress
Medium

Bug Description

See discussion and longer introduction at
https://lists.linux-foundation.org/pipermail/fhs-discuss/2011-May/000018.html

Fortran compilers generate .mod files (when compiling source files which
contain modules), which are similar to precompiled C header files. They .mod
files should be at a defined location to make it simple to use compile
programs.

Linux distributions seem to be a bit lost where to place those files; one finds
several choices, including /usr/include, in some hidden-package-dependent
directory, somewhere in a subdirectory of /usr/lib, or even not shipping them
at all to avoid the issue.

Contrary to C header files and similar to precompiled C header files, the files
are in general compiler dependent, i.e. they should resist in a
compiler(-version) dependent subdirectory of the to-be defined directory.

A possible choice would be /usr/{local/,}lib/finclude/$compilername/
such as /usr/lib/finclude/gcc/x86_64-unknown-linux-gnu/4.7/

Tags: fhs
Changed in mandriva:
importance: Unknown → Medium
status: Unknown → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.