|
From: Samuel H. <sam...@gm...> - 2013-08-26 10:21:17
|
On 26 Aug 2013, at 11:02, Peter Rockett <p.r...@sh...> wrote: > On 26/08/13 10:00, Samuel Halliday wrote: >> On 25 Aug 2013, at 23:36, Earnie Boyd wrote: >>> On Sun, Aug 25, 2013 at 1:17 PM, Sam Halliday wrote: > ...snip >>>> Also, I should note that my .o files are not all Fortran files. Some are also C files. Hence it feels very strange to be using gfortran as the linker. On OS X, the -static-libgfortran works with gcc (but the full path to libquadmath must be called, also with -static-libgcc). >>>> > AFAIU, neither gcc nor gfortran is a 'compiler', nor indeed a 'linker'. > They are both front-ends which, dependent on command line parameters, > invoke a compiler proper, and then a linker to combine the object files. > I think you will find that gcc and gfortran ultimately invoke the same > linker, ld. So not strange at all... That is true, but don't you agree that it is unusual to use gfortran to link objects that are language independent? I much rather use the gcc front-end which is language agnostic. |