From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24044 invoked by alias); 19 Oct 2007 06:40:28 -0000 Received: (qmail 23957 invoked by uid 48); 19 Oct 2007 06:40:11 -0000 Date: Fri, 19 Oct 2007 06:40:00 -0000 Message-ID: <20071019064011.23956.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/33814] Failure of gfortran n Mac Mini In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "burnus 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: 2007-10/txt/msg01660.txt.bz2 ------- Comment #1 from burnus at gcc dot gnu dot org 2007-10-19 06:40 ------- > Whenever I invoke this compiler without specifying a cource file I get the > expected error message: > gfortran: no input files [...] > Whenever I invoke the compiler with a valid fortran source file I get the error > message: > gfortran: error trying to exec 'f951': execvp: No such file or directive. gfortran (and gcc, g++ etc.) are wrappers around the actual compiler. Seemingly, the wrapper "gfortran" cannot find the actual compiler; on my Linux system they are at: /usr/bin/gfortran /usr/lib64/gcc/x86_64-suse-linux/4.2.2/f951 You could try '-v', e.g. gfortran -v -c someFortranFile.f this gives more information, which might help. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33814