From: Wayne Vieira <wavieira@xxxxxxxxxxx>
The man page for sgif90 says that the -cpp option calls the Bcpp
compiler
(?) which locate could not find on my Big Sur system. (/lib/cpp was
there)
I think this is a typo. Should be that it calls "cpp".
The B is probably from the nroff font stuff.
Using this command option generates an error.
sgif90 -cpp test.f
I don't have access to my system at the moment %$#@ Rolling Calif
blackouts!! The error is similar to:
don't recognize '-traditional-cpp'
This was talked about before. It is due to the recent upgrade of gcc,
which no longer accepts that option. The newest, unreleased sgif90
passes -cpp rather than -traditional-cpp to gcc.
As in the example above, I am not using that option, so I must guess
that it
is being passed onto the /lib/cpp. My questiosn are:
1. Is the man page reference to Bcpp an error? If not where does one
look
for Bcpp?
Yes, see above.
2. using -traditional-cpp on gcc will produce a similar error. But no
error appears on sgicc. I have to guess that sgif90 is calling gcc as
it's
pre-processor. Is that correct?
Yes.
Why isn't sgif90 using sgicc??
Because sgicc also uses gcc as its preprocessor :-)
-- Mike Murphy
-- mpm@xxxxxxx
-- quote of the day:
-- "Power is like a narcotic taken to diminish the pain of an empty life"
-- (David Petrescue)
|