From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31702 invoked by alias); 8 Dec 2008 12:52:00 -0000 Received: (qmail 31163 invoked by uid 48); 8 Dec 2008 12:50:38 -0000 Date: Mon, 08 Dec 2008 12:52:00 -0000 Message-ID: <20081208125038.31162.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/35707] Search /usr/local/include and /usr/include for .mod files In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dfranke at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2008-12/txt/msg00733.txt.bz2 ------- Comment #8 from dfranke at gcc dot gnu dot org 2008-12-08 12:50 ------- > A semi-proper place for .mod files is: > /usr/lib64/gcc/x86_64-suse-linux/4.4/finclude/ > (Semi because finclude does not distinguish between e.g. 32bit and 64bit.) One could argue that .mod files are library support files and could be placed/distributed in a project's $libdir?! If there's a difference between 32-bit and 64-bit .mod-files, placing them in their respective $multilibdir would solve this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35707