[Bug fortran/33814] Failure of gfortran n Mac Mini

[Bug fortran/33814] Failure of gfortran n Mac Mini

[mercergeoinfo at yahoo dot co.uk]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33814

mercergeoinfo at yahoo dot co.uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mercergeoinfo at yahoo dot
                   |                            |co.uk

--- Comment #4 from mercergeoinfo at yahoo dot co.uk 2011-10-03 15:16:15 UTC ---
I followed the instructions in the 3rd comment, actually I installed the
suggested binary from the link in point 2 first but the problem persists.
Looking at the contents of 
/usr/local/libexec/gcc/i686-apple-darwin8/4.2.3/
may give an answer, it contains an empty folder called "install-tools".
Any other suggestions for getting gfortran to run on OSX (Lion)?

[Bug fortran/33814] Failure of gfortran n Mac Mini

[fxcoudert at gcc dot gnu dot org]

------- Comment #3 from fxcoudert at gcc dot gnu dot org  2007-10-24 10:09 -------
Hi Peter,

The following:

>  f951 strauss.f90 -fPIC -quiet -dumpbase strauss.f90 -mmacosx-version-min=10.4
> -mtune=generic -auxbase strauss -version -ffixed-form -ffixed-line-length-132
> -fbounds-check -fmax-errors-0 -fintrinsic-modules-path finclude -o
> /var/tmp//ccZtzWga.s
> gfortran: error trying to exec 'f951': execvp: No such file or directory

shows that it's a packaging problem and not a problem with the compiler
codebase. Because you talk about "gfortran-intel-bin.tar", I suppose you use
the binaries from http://hpc.sourceforge.net/, so you should report the problem
to them. Meanwhile, there are 2 things you can do to get a working compiler:

  1. Add /usr/local/libexec/gcc/i686-apple-darwin8.8.1/4.3.0 to you PATH
environment variable. If packaging was correct, this shouldn't be needed, but
in the current situation this will get the compiler working. (NB: the last two
components of the path above may be slightly different; the bottom line is,
find what is the subdirectory of /usr/local/libexec that contains an executable
file named f951)

  2. You can alternatively try downloading the binaries provided by the
gfortran team (well, by me, in fact), at
http://gcc.gnu.org/wiki/GFortranBinaries  They come as an Apple installer
(which might be better or worse, depending on your point of view!) and should
work out of the box.

Since this is not a bug in GCC/gfortran, I'm closing this bug-report.


-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fxcoudert at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33814

[Bug fortran/33814] Failure of gfortran n Mac Mini

[cbas25 at strath dot ac dot uk]

------- Comment #2 from cbas25 at strath dot ac dot uk  2007-10-19 15:25 -------
Thank you for the prompt response

I have taken your suggestion about including "-v" in the command line.
I have compiled the source of the program (strauss.f) with both the g77 nd
gfortran compilers.  Incidently the code has compiled succesfully on linux
systems both 32 bit and 64 bit.

With the added "-v" the results were as follows:

With g77:
Driving: /usr/local/bin/g77 -ffixed-form -ffixed-line-length-132 -fbounds-check
-ffortran-bounds-check -v -w -ff90 -o strauss strauss.f -lfrtbegin -lg2c
Reading specs from /usr/local/lib/gcc/i686-apple-darwin8.8.1/3.4.0/specs
Configured with: ../gcc-3.4.0/configure --enable-languages=f77
Thread model: posix
gcc version 3.4.0
 /usr/local/libexec/gcc/i686-apple-darwin8.8.1/3.4.0/f771 strauss.f -fPIC
-quiet -dumpbase strauss.f -mtune=pentiumpro -auxbase strauss -w -version
-ffixed-form -ffixed-line-length-132 -fbounds-check -ffortran-bounds-check
-ff90 -o /var/tmp//ccT7pus3.s
GNU F77 version 3.4.0 (i686-apple-darwin8.8.1)
        compiled by GNU C version 3.4.0.
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
 as -arch i386 -o /var/tmp//ccbScj9o.o /var/tmp//ccT7pus3.s
 /usr/local/libexec/gcc/i686-apple-darwin8.8.1/3.4.0/collect2 -arch i386
-dynamic -w -o strauss -lcrt1.o -lcrt2.o
-L/usr/local/lib/gcc/i686-apple-darwin8.8.1/3.4.0
-L/usr/local/lib/gcc/i686-apple-darwin8.8.1/3.4.0/../../.. /var/tmp//ccbScj9o.o
-lfrtbegin -lg2c -lgcc -lSystem |
 c++filt


With gfortran:
Driving: /usr/local/bin/gfortran -mmacosx-version-min=10.4 -ffixed-form
-ffixed-line-length-132 -fbounds-check -fmax-errors-0 -v -o strauss strauss.f90
-lgfortranbegin -lgfortran -shared-libgcc
Using built-in specs.
Target: i386-apple-darwin8.10.1
Configured with: ../gcc-4.3-20070810/configure --enable-threads=posix
--enable-languages=fortran
Thread model: posix
gcc version 4.3.0 20070810 (experimental)
 f951 strauss.f90 -fPIC -quiet -dumpbase strauss.f90 -mmacosx-version-min=10.4
-mtune=generic -auxbase strauss -version -ffixed-form -ffixed-line-length-132
-fbounds-check -fmax-errors-0 -fintrinsic-modules-path finclude -o
/var/tmp//ccZtzWga.s
gfortran: error trying to exec 'f951': execvp: No such file or directory


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33814

[Bug fortran/33814] Failure of gfortran n Mac Mini

[burnus at gcc dot gnu dot org]

------- 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