In article
nwrddc01.gnilink.net>,
"Carlie J. Coats" jyarborough.com> writes:>
> Quite clearly, you did not read the page you downloaded it from,
That is correct. I was expecting installation instruction to
be contained with the package. The missing instructions is
clearly a bug.
> nor the header-comment of the Makefile itself.
Actually, I did scan the Makefile. There are no instructions
to set the various variables. There are only definitions.
The default settings are anything but user friendly.
> And also quite clearly
> the "gcc" language manual specifies a space between the "-o" and
> the output-file name.
The manual also doesn't specify that the space is required. The
manual is written for clarity. It is also apparent you've never
used getopt(3), which states
The option string optstring may contain the following elements: individ-
ual characters, and characters followed by a colon to indicate an option
argument is to follow. For example, an option string "x" recognizes an
option ``-x'', and an option string "x:" recognizes an option and argu-
ment ``-x argument''. It does not matter to getopt() if a following
argument has leading white space.
> Nor does this explain why the very same compile command-line
> options work perfectly-well with just a ".f" but do
> NOT work for SOME files when invoked from a different directory
> and an absolute path name for the source file.
You need to post an exmaple because your Makefile system doesn't
work even when the environmental variables are set.
Finally, I'll note that the fortran at
gcc.gnu.org address isn't
too difficult to find. In the 6 years, I've been subscripted to
the list, I cannot recall a single post from you about your
problems with gfortran. gfortran developers can't fix if your
refuse to communicate with them.
--
steve
